Core 'Harbour dynlib' creation has been integrated into
the make system, so such customized harbour dynlibs aren't
supported by core build process anymore.
I believe such customized Harbour dynlibs should be rolled
by those few users who require it by their own, firstly
because it breaks the separation of core/contrib areas,
secondly because 'harbour dynlib' should provide a standardized
interface and set of functionality, so that they are
interchangeable and won't cause any mess when different
copies are installed onto the same system (dll hell).
If someone needs such customized dynlib (which shouldn't
normally be called harbour.[dll] anymore), can be created
using regular tools or still provided hb-mkdyn.sh script.
BTW, technically it could be solved probably (by investing
another big amount of time), but for above reasons I
rather plan to think/work on allowing to convert any contribs
into separate .dlls. (like hbct.dll, hbct.so)
Brgds,
Viktor
On 2009.09.01., at 6:46, Lorenzo Fiorini wrote:
I've just resync my local repo after vacation and I've found that in
hb-func.sh the lines below are commented:
# echo "Making ${full_lib_name}..."
# ${hb_mkdyn} ${full_lib_name} ${LIBS} ${linker_options}
# if [ "${LIBS}" != "${LIBSMT}" ]; then
# echo "Making ${full_lib_name_mt}..."
# ${hb_mkdyn} ${full_lib_name_mt} ${LIBSMT} ${linker_mtoptions}
${linker_options}
# fi
I've read in the Changelog that:
...
* bin/hb-func.sh
- Commented creation of dynamic libs. Now it's done on GNU Make
level.
But now I can't find a way to add contrib libs to libharbour.so.
Any suggestion?
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
