Hi,
I'm really sorry but I was wrong. I've just tested current SVN
and default build time CC is preferred.
that is contrary to what i'm experiencing. i've built hb in cpp mode
(so it was using g++ as the compiler), and if i don't explicitly
specify "-cpp" to hbmk2, it will call "gcc".
The compiler (GNU C/C++) is properly selected, but the
*build mode* is not inherited, just like any other Harbour
build options (besides custom compiler flags, which is the
only exception here, but even this could argued upon).
my (and i think yours too, and i think viktor's too :), at least
that's what i gather) view is that if nothing more specific
instruction is given to hbmk2 (ie no -cpp, no -comp, no whatever else
you can tell it what to use), then it should invoke the compiler it
was compiled with.
This wouldn't work out too well for non-*nix compilers,
so unless we want to deepen the differences between platforms
(my goal is the exact opposite), with all the consequences,
plus see my two questions in my answer to Przemek, I'd like
to keep it the way it is now.
I assume sources compiled in C and C++ mode *can* work together,
so we shouldn't force users to change build mode just because
Harbour happens to be built in another mode (C++).
What we should rather try to solve in hbmk2 is how to fix
linkage of objects with mixed C and C++ mode. This would
be far more useful than tweaking default mode.
Notice that even if hbmk2 would inherit build mode, it'd
still be very easy to break it, by simply manually overriding
the default mode, which in some cases may be a necessity to
compile certain sources.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
