On Jan 25, 2007, at 2:58 PM, Graham Dunn wrote:
> I have a basic (and I mean *basic*) XSLT that will transform a .vcproj
> to a build.xml, but I was hoping not to have to further re-invent
> the wheel.
> I started with this article, which has some basic support for
> vcproj->build.xml files:
> The limitation in their approach was that you can only specify a
> configuration (Release|Win32/Debug|Win32, etc), rather than having
> multiple targets created in the ant file.
There is a bit of philosophical difference that makes it fairly
simple to have a good Ant build generate a good VC project file (file
separator issue not withstanding) while making it difficult to do the
reverse. Ant builds, whether Java or C++, are generally wildcard
driven (compile all *.java files or *.cpp files in some specified
directory tree) where VC projects (like Make files) have an explicit
listing of files. The wildcard approach eliminates the need to
continually update the make file every time a new file is added and
also discourages the presence of zombie files in the source tree.
Any ideal project->Ant tool would try to create the simplest fileset
that would be equivalent to the explicit list of files.
Sorry about the slow response, I'll try to commit the VC 7.x change
shortly. I'm trying to get log4cxx ready for a release and that will
likely mean that I will try to have a corresponding cpptasks release
and will try to work through the bug list.