+ - Advice / suggestions on Windows Build Environments
Submitted
by
blackcoot
blackcoot writes "I find myself faced with the unenviable position of needing to port a lot of heritage C / C++ code developed using a mishmash of external and internal dependencies to Windows. The objectives of the port are:
1) Allow our Windows devs to work comfortably in Visual Studio (support for other IDEs is desirable but not a requirement)
2) Minimally painful support for the Platform SDK / Windows SDK
3) Minimally painful support for other SDKs (specifically, Boost and VXL)
4) Support cross platform development with the native tool kits. This can either be done in a qmake / automake style, where platform specific build files are automatically generated or fully integrated a la SCons
5) Allow building independent modules in an independent fashion so that we can cherry-pick dependencies
So here I am, I turning to the /. community: what has worked for you as a build system under Windows? What hasn't worked? What important lessons did you learn along the way?"
1) Allow our Windows devs to work comfortably in Visual Studio (support for other IDEs is desirable but not a requirement)
2) Minimally painful support for the Platform SDK / Windows SDK
3) Minimally painful support for other SDKs (specifically, Boost and VXL)
4) Support cross platform development with the native tool kits. This can either be done in a qmake / automake style, where platform specific build files are automatically generated or fully integrated a la SCons
5) Allow building independent modules in an independent fashion so that we can cherry-pick dependencies
So here I am, I turning to the