now with libharbour*.so installed in /boot/common/lib/harbour/,
things
don't find it.
Not now but from the beginning of adding default HAIKU localization
it was installed in:
HB_INSTALL_PREFIX=/boot/common
${HB_INSTALL_PREFIX}/bin/
${HB_INSTALL_PREFIX}/lib/harbour/
${HB_INSTALL_PREFIX}/include/harbour/
In general it's a work in progress and in final version we will have
soft
links (just like now in other *nixes) or we will store static and
dynamic
libraries in different directories. See recent Viktor's modifications.
We should agree here few things:
1. what is system wide localization and what user customized and how
to detec them.
Yes.
2. what directory structure we should use for both type of
installation
respecting multi C compiler or cross build binaries. We should also
define data directory for Harbour system wide installation. I do not
like current situation that:
druzus:~# ls /usr/bin|wc -l
3213
druzus:~# for f in /usr/bin/*; do [ -x $f ] || echo $f; done
/usr/bin/hbmk.cfg
druzus:~#
storing configuration files in system wide binary directories
is unacceptable for most of distributions.
Note that hbmk2 already supports several system locations,
so we're free to store it anywhere.
I'd add some more things here:
- where to put 'contrib', 'addon' dirs as separate entities, so that
they don't get mixed in core libs/headers/etc.
- where to put docs, examples.
- where to put INSTALL, Changelog, ERRATA, TODO and COPYING.
3. where to put static and shared libraries (now it's possible
to set different localizations) and/or where create soft links.
Yes.
+1: How to name them. Current naming is more or less unified
for non-*nix, but for *nix we have the darwin world and the
rest, which are different in several ways. Maybe this is normal,
but I'd like to know for sure.
4. shared library naming convention - now only Darwin build tries to
respect correct version setting in names and links.
:) yup, see above.
5. how to merge binaries for different C compilers and/or different
platforms (cross building) and how user should chose preferable
C compiler or destination platform.
Yes, for non-*nix, the system is to use:
bin/<arch>/<comp>/*
or
bin/<arch>/*
for bins.
and
lib/<arch>/<comp>/*
for libs.
I think we should define it ASAP to reduce number of necessary
modifications for users which tries to follow SVN modifications
and sync his local repositories with SVN quite often.
Agreed.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
