Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » Managed Build System extension configuration
Managed Build System extension configuration [message #93140] Mon, 02 February 2004 10:09
Eclipse UserFriend
Originally posted by: cor.nospam.nospam.geboers.telenet.be

Hi,

I am using CDT 2.0 to do compiles with another compiler then the gcc on
Win32. This works fine with standard makefiles, and I added an extension
that even works with the "Managed Build".

In my extension plugin.xml, I add the command for the C Compiler (c89) and
it is used to generate the makefile, which compiles the code correctly. In
order to avoid that I have to put my compiler on the PATH however, I would
like a user to be able to choose a version of the compiler through the
preferences window. I got the code to make this work in place, but I am
struggling now with how I can tell the MakefileGenerator to use the
command that is entered on the preferences page. It seems to insist on
using the command specified in the 'plugin.xml'.
I worked around this by specifying the command as "$(C89COMPILER)", which
tells the make utility to use the env. variable C89COMPILER as it's
compiler and this works also, but it is less elegant then specifying the
command in the preferences (or project properties) page.

The reason I need is that, depending on the target OS-version, I need a
different c compiler and I would like to be able on a project base to set
the correct compiler location.

A workaround could be if I could set the env. variables from within my
property page. Any body know if that can be done ?

Cor
Previous Topic:Install CDT2.0M6 as root, no run as user
Next Topic:CDT birds-of-a-feather at EclipseCon
Goto Forum:
  


Current Time: Sun Apr 27 02:11:37 EDT 2025

Powered by FUDForum. Page generated in 0.01761 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top