i see it's to check for the presence of png.h, and such techniques
are
used elsewhere too. would filtering /usr/include out of the include
list be too cumbersome?
I'm not sure I understand. Could you tell some more about this?
what i mean that after all the magic is done, it ends up with a
command line like that:
cc -I. -I../../../../../include -K udk -KPIC \
-I../../../../../source/hbzlib -I/usr/include -c \
../../../_hbhbpdf.c -o_hbhbpdf.o
(wrapped for clarity). would it be too cumbersome to by some means
filter out the '-I/usr/include' part, so that it in the end it will
not be part of the actual command line?
Okay I think I see, though such filtering is already implemented.
In the final cmdline HB_INC_LIBPNG_OK is included which contains
only those dirs where png.h could be found. If it shows up in
your cmdline, chances are high there is /usr/include/png.h present.
If not, we should check how that can happen.
See line HB_INC_LIBPNG_OK += $(foreach ...
[ OFF: Actually '+=' should better be ':='. I'll fix these later. ]
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
