> Ah. Correct again! I thought if the gcc version I wanted to use before any > other was first in the windows path, it would only be used... but I am > incorrect. > > # proper > ! HB_COMPILER: mingw (v44) (autodetected: c:/mingw/bin/) > > # problematic > ! HB_COMPILER: mingw (v45) (autodetected: c:/mingw/bin/gcc.exe > C:/strawberry/c/bin/) > > If it detected Strawberry Perl's gcc version after mine, which it seems like > it did as it comes 2nd on the above printout.... can't the version detect / > only use the first one, c:/mingw/bin/gcc.exe?
I'm afraid not. In general it's not very good to mix different compilers in PATH, but it's especially not good mix two different gcc versions in PATH at the same time. INSTALL doc makes this very clear. There is no compiler selector logic in our build system, since it would be a complete nightmare to test (hundreds of different combinations) and maintain just to sort out otherwise not very likely configurations as above. Notice that mixing compilers is not only bad for Harbour, but it's generally bad practice on Windows systems. Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
