I decided to follow an extremely simple pathwhen building source codes. The path isbased on bat files
instead of make files.
For example, this is how abat file for compilationof all test caseslooks like for a MinGW C/C++ compiler
and Win32 platform and Release configuration:
@echo ***Compiling with MinGW v3.4.2 ***
@echo ***Configuration - Desktop - _WIN32_MGW - RELEASE ***
@g++.exe -B ../../AppsSca -DNDEBUG -o Release\MgwTestApp.exe MgwTestApp.cpp
A project is organized insuch away that compilation starts from 'MgwTestApp' and all the rest will be
"attached" through a well designed set of configuration cfg files,header files, etc. That approach
guarantees integrity of all subsystems because they arealways re-compiled. Since modern computers and
C/C++ compilers are veryfast this is not a problem at all.
My apologies - I am new to the forum and had no understanding of how private worked (I thought a response to a private post would automatically be private for example).
I like Make, but it does require a lot of work to maintain. Autoconf has been extremely useful for us for working on three platforms: Linux/GCC, MacOS/?CC, Win7-64/MinGW but as you said it can't seem to handle the microsoft (or Intel) tool chain.
As there is not drop-in replacement compiler for what we're doing, I will likely stick with MinGW under Windows. I could compile a few DLL's selectively using the Intel compiler.
I found the following web page very helpful (not sure if I already posted it). Just in case anyone else is searching for an answer to the same question I had: