[cdt-dev] Managing additional toolchain state

[Scott Michel <scottm@xxxxxxxx>]

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... :-)