William A. Rowe, Jr. wrote:
So we need to choose a language just to create these files. What do we trust? I insist we be able to execute it on unix in order for anyone to package win32 builds. One main app, one per-project template module (e.g. apr, libapr apr-util etc) and a module-per- environment which can stuff up the file.
What are the per-project templates? If they came [mostly] from the unix build schema, we would be in hog heaven.
Perl and java are installed most everywhere, python is catching up, .NET is here on modern Windows boxes but most unix boxes don't have mono installed. I'd like this to be painless as possible.
A while back I had posted the beginnings of a patch to gen_make.py that used ezt.py to templatize the existing win32 build system, making it automatically generated. This could easily be extended to generate other types of build files, if someone was motivated enough to continue the work. I never did because I don't actually have access to a win32 system to test things on, and none of the win32 developers ever got back to me with confirmation on whether things worked or not.
Note that this is how Subversion's win32 build works, and it allows us to build with various different versions of visual studio just fine.
-garrett
