Hi Przemek,
Just some quick reaction, I have to go now.
and HB_ETC_INSTALL or HB_CNF_INSTALL.
What is the difference between ETC and CNF?
If possible IMO we should not differentiate between
types of config files.
/lib/
<native_harbour_libraries>
[/<addon_harbour_lib>/
<native_addon_libraries>]
[/<platform>/<cc>/
<platform_cc_libraries>]
I suppose 'contrib' counts as 'addon'.
IMO and if system rules allow it, we should put native
libs also under plat/cc structure, since generally speaking
we may support multiple compilers with incompatible lib formats
(like watcom and gcc, or anything else in the future).
Plus there must a plat/cc structure also below each addon.
The shard library naming convention
===================================
@ - softlink
* - hardlink
@<pref><name><epoc>.<ext> ->
@<pref><name><epoc>.<ext>.<major> ->
@<pref><name><epoc>.<ext>.<major>.<minor> ->
*<pref><name><epoc>.<ext>.<major>.<minor>.<rev>
<pref> is library name prefix,
'lib' in supported by Harbour *nix systems
<name> is base name, 'harbour' in our case
<epoc> is used to mark new or alternative branches, we are using
'mt' to mark alternative libraries with MT support.
<ext> is library extension,
'dylib' in Darwin,
'sl' in HP-UX,
'so' in others.
<major>, <minor>, <rev> - version numbers (i.e. 2.0.0 for current
SVN).
i.e.:
@libharbour.so ->
@libharbour.so.2 ->
@libharbour.so.2.0 ->
*libharbour.so.2.0.0
Real/suggested usage in supported *nixes:
Linux, Solaris, Haiku, NetBSD:
@<pref><name><epoc>.<ext> -> *
@<pref><name><epoc>.<ext>.<major> ->
*<pref><name><epoc>.<ext>.<major>.<minor>.<rev>
FreeBSD (some packages use Linux like form):
@<pref><name><epoc>.<ext> ->
*<pref><name><epoc>.<ext>.<major>
OpenBsd:
*<pref><name><epoc>.<ext>.<major>.<minor>
Darwin???
On darwin the current naming seems to be the accepted one,
although some libs use '-' to separate name form version no.
[ I've just browsed my /usr/lib dir for above conclusion,
so I don't know what's the official standpoint here, anyway
I'd assumed the extension is fixed. ]
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
