Re: [cdt-dev] Visual C++ Build Integration

[Dmitry Nezhevenko <dion@xxxxxxxxx>]

On Sat, Jul 31, 2010 at 10:42:01PM -0400, Doug Schaefer wrote:
> Hey gang,
> 
> I'm having a spurt of productivity tonight and have entered another
> enhancement for a plan item for CDT 8.0. This one is to complete the
> build integration plug-in that I started long ago for Visual C++. The
> driver for this is that, thanks to the work Eugene has done on the
> reference TCF agent, we have a good start at a Windows debug
> integration. I'll be working on bringing that to completion too and
> give us a pretty good Visual C++ story.
> 
> The bug is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=321445
> 
> BTW, the focus for this integration is the Windows SDK version 7.0 and
> anything they release later. We could add Visual Studio, assuming it's
> different, in the future.

What I want to ask is about how it will work (in future)? Will it be able 
to parse/read/build visual studio solution files? Or it's just about
toolchain.

A lot of c++ devs are forced to use visual studio on win due to it's
project files. It will be very cool feature to have some minimal (read
only) support of MSVC solutions. Like build/clean project/solution/current
source file. So MSVC here is just a "custom" build system.

And same applies sometimes also for apple's Xcode projects. They sucks
much more than MSVC...

Maybe it's better to introduce some kind of "universal" non-managed build
system that will have configurable commands for
building/autobuilding/cleaning/etc? And maybe even hooks for "file/class
added/removed".  Something not dependent on particular build system at
all. This allows easy integration with very custom systems in case if user
is able to write a few "helper" scripts.   

Btw, are there any plans to support "compile/preprocess single file"?

-- 
WBR, Dmitry