Hi, >> There is a better solution: See my just sent e-mail. > > I just did, and I'm a little confused here: > > I have (in the same Windows machine) several C/C++ compilers: > > - MSVC ( 8 & 9 versions ) > - MinGW > - BCC > - OpenWatcom > > If I remove the HB_COMPILER option then the build process at > Harbour detects the compiler as MinGW. > > So in my case, I have to manually set the HB_COMPILER option.
So set it, and also set HB_COMPILER_VER accordingly. It's always a good practice if you want to make sure proper build options are used by Harbour build process and hbmk2. There is no way to make up a default which works properly for everyone. I'd however not recommend keeping that many tools in the PATH at the same time. It can be source of many strange build errors, even with Harbour. It's also a basic recommendation in INSTALL. BTW this rule applies even more so for other 3rd party package, so it's not a Harbour thing or my invention. Locally I use small batch files to setup the environment for the compiler I'd like to use at any moment, f.e.: 'mi hbmk2 hello.prg', to select mingw and build something. > The file at "config/win/msvc.mk" says: > > ifeq ($(filter $(HB_COMPILER_VER),600 700 710 800 900),) > RCFLAGS += -nologo > endif > > So, what value I have to give to HB_COMPILER_VER to > do not execute the "RCFLAGS += -nologo" ? Next time there might be other options which depend on compiler version, so I don't want to remove this. At least the problem isn't hidden now. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
