Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Managing additional toolchain state

Hi,

It's not clear to me what you are trying to do, but I'll give you some
thoughts and maybe they'll help.

The managed build system allows you to define tools (e.g. compiler,
linker) and their command line options.  I don't know what you mean by
"I created a properties page for this module def file".  Do you have a
tool that creates module definition files, or does your user use a text
editor to create the file?  If there is a tool, then you can define the
tool in your tool-chain definition.  If the file is simply a text file
that is input to the linker, you can define your own linker tool that
has an additional option for specifying the name of the module
definition file.  That option can generate whatever command line option
is needed by the linker (e.g. /def:filename).

Regards,
Leo

-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
Behalf Of Scott Michel
Sent: Thursday, January 20, 2005 9:48 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Managing additional toolchain state

Question: How does one go about managing additional toolchain state 
within the current CDT structure? As an example, I'm creating a plug-in 
for the Digital Mars C/C++ compiler, and its linker depends on a "module

definition" file to properly create binaries for Win32.

I created a properties page for this module def file, but now, I'm 
wondering how to hook this additional state into ManagedBuildManager or 
how to get an object invoked to track this additional plug-in build 
state. It'd be even better if I could subscribe to events involving the 
file, but I'll settle for whatever I can get.

Any suggestions? Pointing me at some code for ideas will help.

I did look at "cextension", but didn't quite see how I could get CDT to 
create the the cextension object on my behalf automagically.


-scooter
  (preparing to be flattened by the deafening silence... :-)
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top