On Wed, 16 Sep 2009, Szak�ts Viktor wrote:
Hi,
> It's a little messy ATM. On *nixes there is no autodetection
> when doing native builds, it will default to the C compiler
> used to build hbmk2 itself (this what you ask for, so I wonder
> why doesn't it work for you, but you didn't tell the platform).
> For cross builds there is autodetection of cross-tools if you
> specify target platform, there isn't if you specify target
> compiler.
I'm really sorry but I was wrong. I've just tested current SVN
and default build time CC is preferred.
I'm "nearly" sure that few weeks ago it was a problem and I had to
update my build scripts, i.e. OpenWatcom was preferred when I had
in my envvars:
export WATCOM="/home/nwe/lng/watcom"
export INCLUDE="${WATCOM}/lh"
export PATH="${WATCOM}/binl:$PATH"
Now this happens only in pure Harbour build system (make) but I can
leave with though I'm not sure it's good choice for default behavior
because we will chose some rather platform exotic compilers if they
are installed instead of system default one.
Current hbmk2 behavior is OK for me - thank you very much and I think
we should only add support to "inherit" C++ mode from Harbour build
settings.
BTW you or Tomaz asked about using OpenWatcom in Linux. Current version
(1.8) in full installation contains binaries for DOS, WIN, OS2 and
Linux builds. It's enough to set executable attributes for Linux
binaries in ${WATCOM}/binl directory.
> On non-*nix there is autodetection for most native compilers
> (some, like pocc64/poccarm are missing yet). If none can be
> detected, it will look for embedded installations based on
> target platform. It will also look for embedded installations
> if user explicitly selected the compiler.
> You can check the order of detecting different compilers in
> variables aCOMPDET and aCOMPDET_EMBED.
> I plan to rework autodetection to solve all current problems
> in an easier to oversee way, current state is rather organic,
> and misses some extras we have in GNU Make (although it has
> others).
Addressing all issues is horrible problem. Now you collected most
of information so you can try to create some more common and simple
rules which can be easier to guess/follow by users what I agree is
very important. Anyhow it's still huge job and thank you very much
for your all affords and final results which are fantastic.
best regards,
Przemek
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
