Your plugin definitely sounds interesting
and would complement the prototype Win32 debugger nicely. Doug Schaefer is
doing the Win32 debugger in his spare time, you should ping him if you have
questions about it or would like to contribute to it.
Personally I don’t see a problem in
theory with your toolchain becoming a part of CDT somehow, as long as it works
with CDT 3.0, and as long as it’s going to be maintained. Since the 3.0
release is going into the release candidate cycle soon it’s probably most
appropriate to think of this as a potential activity that we’d look at
post-3.0
Perhaps once your plugin is finished you
could demo it for us so that the build committers and other interested parties
could have a look at it.
___________________________________________
Chris Recoskie
Texas Instruments, Toronto
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Emiliano Lesende
Sent: Tuesday, June 07, 2005 7:18
PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Microsoft
VisualC++ toolchain
Is anyone interested in
this?
On 6/6/05, Emiliano
Lesende <emiliano.lesende@xxxxxxxxx>
wrote:
For the past few weeks I've been developing a new plug-in which includes
Microsoft VisualC++ toolchain, including but not limited to:
- NMake makefile generation
- Scaner configuration discovery profile
- Environment supplier
- Automatic configuration
I'm very close to finish the plug-in; is it possible to contribute back to CDT?
Who should I talk to? I would mantain this plug-in, and also I would like to
became an official developer for CDT.
One more thing, I saw on CVS that there is a Win32 debugger on the works. I
tried it but hangs misserably trying to set a breakpoint. Who is reponsible for
this code? I would like to help coding it and testing.
Best regards,
Emiliano Lesende