Thanks for the review and feedback, Bill. I agree with your assessment of the floodenv.bat changes to invoke other programs. In my dealings with DevStudio DSP files and NMAKE makefiles, I've always found myself juggling environment variables with similar contortions.
Do we need to support the IDE environments with DSP/DSW files (and also the newer IDE formats)? As the IDE-based file formats have changed over the course of several VC++ releases, NMAKE has remain consistent. I've also found it easier to maintain the NMAKE makefiles than the DSP files (stable syntax, consolidate common settings in include makefiles, less noise than IDE-generated files, etc.). So, I advocate keeping the build system in NMAKE makefiles. If we do need to support IDE users, I would have the DSP invoke the NMAKE makefiles and specify debug/release. The goal is to keep the compiling and linking in the NMAKE makefiles. ------- Original Message Dated: Tue, 04 Feb 2003 10:33:24 -0600 | From: "William A. Rowe, Jr." <[EMAIL PROTECTED]> | | I liked the earlier patch to enable/disable OpenSSL. But the patches | below indicate why we don't use batch files... we can't go digging | throughout the system and order the various VisualStudios and | PlatformSDKs correctly; that has to be up to the developer. | ... | The update to VisualStudio 6.0 format? +1 | Cleaning up the SSL envvars list and detection? +1 | Using floodenv as an 'invoker' of make? --1 | ...
