Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Binary Parsers API

Follow the chain of @deprecated's from CCorePlugin.getBinaryParser() to the apparent replacement getDefaultBinaryParserExtensions() which returns an array of ICConfigExtensionReference's which have a method getConfiguration() which return an ICConfigurationDescription.

The good news, I think, is that my focus should be on CModelManager.getBinaryParser() which feeds into the IBinaryFile creators. I can do a similar thing that I did with scanner info and check if there are any new-style build configs and do something more appropriate for them. I should be able to play with BinaryParserConfig without breaking things, I think...

On Fri, May 6, 2016 at 11:22 AM, Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx> wrote:
Can you give a code location where you see the "leak"? Binary parsers can be specified per project along with their toolchain defaults, so it wouldn't be too surprising that ICConfigurationDescription got in there.


From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Doug Schaefer [cdtdoug@xxxxxxxxx]
Sent: Friday, 06 May 2016 11:15 AM
To: CDT General developers list.
Subject: [cdt-dev] Binary Parsers API

Hey gang, one thing I realized as I was trying out the new remote launch is that I don't have binary parsers turned on with my new build configs.

Looking at the core APIs to get them, I see that ICConfigurationDescription has leaked into them as well. As I try to figure out what was so wrong with getting binary parsers by id, I may have to make some API changes there. I'll know early next week.

If anyone has experience they want to share to help me understand the intent, please let me know.


cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top