Okay I understand it this way. This is expected behavior as it
detected your own C compiler installation (msvc), so it didn't
use the embedded one. We can change priorities if this isn't
no need, "compiler" switch to force compiler is ok, i just wanted to
inform that there is "broken-link" betwen installation/setup where i
selected during installation/setup not-to-expand msvc binaries [i
wanted just embedded mingw] and run time hbmk2 which detected
existing msvc compiler and defaulted to it although there were no
previously expanded binaries for it, that's all.
idea is, if one select at install time no-msvc than to prepare
config for hbmk2 not-to-set-msvc-as-default-even-if-there-is-msvc
I'm thinking the other way round: If someone has MSVC
installed (and I believe MSVC doesn't get installed
without user's knowledge), it's expected from user to
choose MSVC libs.
Maybe later someone else or I will add a feature to
toggle each target platform compiler to add such extra
level of configuration, but to me this seems to make
it too much complicated and creates another factor to
consider in every scenario (f.e. what if someone just
copies/installs MSVC libs afterwards? What if MSVC libs
are distributed separately)
Next level could be that hbmk2 verifies if libs are
actually available for a given detected target, and
if not, it skips it. Probably that's the solution
which need to be implemented, but not now.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
