Hi Przemek,
On Wed, 02 Jul 2008, Szakáts Viktor wrote:
Let's make this more granular. For the builds I've tried,
both hbsqlit-s work okay, so I see no reason to exclude them as is.
Same goes for hbziparch, which worked for me under Win32/BCC.
Then please include them when you will make BCC binaries.
I only want to exclude from contrib/Makefile libraries
which cannot be cleanly compiled so by default:
make install
should make clean build without any warnings or errors.
If you want to create additional libraries which cannot
be cleanly compiled if will be enough to set HB_CONTRIBLIBS
or execute
make install
in given contrib library directory.
Can we please do this after RC2? Or cannot we add some
hacks to exclude it locally?
I simply don't want to retest the whole build process
and start to mess with manual contrib override, because
of this modification.
This problem was obvious since months, so if we want
to change it let's give it some more though and let's
do it with the less impact this close to RC2.
And they don't for some compilers. hbsqlit* cannot be compiled
by any C++ compiler and hbziparch cannot be compiled by any C
compiler which does not also support C++ mode. So they work only
for chosen builds and only for such builds should be enabled.
If we clean hbsqlit* then IMHO they should be included.
The hbziparch is different problem. IMHO instead of investing
time in this library we should extend hbmzip and add missing
functionality.
I don't personally care about hbziparch, I don't use it,
and don't plan to use it, it's probably the ugliest code
in whole Harbour. I use hbmzip, too. Yet it seems to be
a popular contrib.
I don't know, let the group decide.
In any case, you can disable it for additional platforms,
compilers as you wish.
Unfortunately I don't, I only have Darwin. BTW, if you need
an account on either of my Macs (one PPC, one Core2), I can
set it up for you for SSH access. Just tell.
If you will still have the problem with MacOSX builds then I will
have to ask you about it.
But first please try to redirect stderr to file, f.e.
./make_gnu.sh 2> log_drw.err; set >> log_drw.err
and send it to me. Maybe it will have some warnings which
tell us what is wrong.
I got that part okay.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
