Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] How does CDT internal builder construct the command line and is there any way to change it?

Ouch. That'd be tough and is one of the issues I have with the command handler, the lack of context you have when it gets invoked.

On Tue, Apr 13, 2010 at 10:59 AM, Anna Dushistova <anna_dushistova@xxxxxxxxxx> wrote:
The problem is that I need my macros($(CC),$(TARGET_CFLAGS)) in the makefile as is
but at the same time I need them expanded when "build selected files" is happening.


On Apr 13, 2010, at 6:39 PM, Doug Schaefer wrote:

Hi Anna,

I have an example of that in the plugin which is found in the org.eclipse.cdt/all folder. You can associate a command line handler for your tool. For the crossgcc one it prepends the gcc prefix, e.g. arm-eabi, as found in the toolchain options.

BTW, the mechanism is a bit weird. If you have any suggestions (or patches :) to improve it, they'd be appreciated.


On Tue, Apr 13, 2010 at 3:54 AM, Anna Dushistova <anna_dushistova@xxxxxxxxxx> wrote:
Hi All,
I'm integrating a custom generic toolchain into CDT.
I have makefile variables in the toolchain definition and all the customization goes through enviroment variables.
Building project works fine, but not building "selected files".
Apparently there is a different builder used for that and it doesn't work with my toolchain definition.
Is there any way I can extend/overwrite/plug into the command line creation process in this case?


Dr. Anna Dushistova
Mentor Graphics Corporation
Embedded Systems Division

cdt-dev mailing list

cdt-dev mailing list

cdt-dev mailing list

Back to the top