Hi Lorenzo,
Yes could be done (see my just sent mail to Francesco on this topic),
however in this case we take the burden of dealing with internal dir
structures of external packages. Unfortunately situation is not as clean
for all packages and for all distros, so any script should either do guess,
do autodetection, or we must require usage of certain standardized
distribution packages for Harbour. This latter won't cover stuff like ADS
and BLAT, and probably other non-GNU stuff.

To sum it up:
- For users it's the best / easiest to offer HB_DIR_ option only.
- For Harbour we need to deal with INC, LIB (for .libs) and BIN (for
.dlls) dir.
- These dirs aren't standarized for all packages and they won't be.

One solution is to create scripts (batch and bash) which would to
the conversion from DIR to INC/LIB/BIN (using autodetection). And
the make files would continue to use what users supply. For a start,
this could be part of the make_gnu.* scripts to not pollute the
contrib dirs with these things. [ of course Makefiles already do some
level of autodetection for *nix system. ]

Brgds,
Viktor

On Sat, Feb 28, 2009 at 10:17 AM, Lorenzo Fiorini <[email protected]
> wrote:

> In gnuwin32 is standard that a lib is installed as:
>
> <path>\bin
>          \lib
>          \include
>
> so I use HB_DIR_x/lib to prefix the libs for the link, HB_DIR_x/bin to
> prefix the dlls and in every contrib makefile I have:
>
> ...
> ifneq ($(HB_DIR_GD),)
>   HB_INC_GD = $(HB_DIR_GD)/include
> endif
> ...
>
> in this way I define only where I installed the lib using HB_DIR_x
>
> It could be:
> ...
> ifeq ($(HB_INC_GD),)
> ifneq ($(HB_DIR_GD),)
>   HB_INC_GD = $(HB_DIR_GD)/include
> endif
> endif
> ...
>
> Just an idea.
>
> best regards,
> Lorenzo
> _______________________________________________
> Harbour mailing list
> [email protected]
> http://lists.harbour-project.org/mailman/listinfo/harbour
>
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to