> On Mon, 30 Nov 2009, [email protected] wrote: >> Log Message: >> ----------- >> 2009-11-30 13:49 UTC+0100 Viktor Szakats (harbour.01 syenar.hu) >> * config/global.mk >> * config/bin.mk >> * src/rdd/Makefile >> * Moved central RDD related information to local makefiles. >> - Deleted support for $(HB_DB_DRVEXT) envvar. >> To extend Harbour with RDDs these should be added as >> regular addons, and optionally hbrun rebuilt using hbrun.hbp. >> [ $(HB_DB_DRVEXT) is still used from hbmk script, I didn't >> touch that part. ] > > How I can make it part of harbour.so library?
I guess the same applies as for all other non-core stuff which users want to place into Harbour dynlib. At this time I don't know what is the generic solution for this, but to me it's still an alien idea to create customized Harbour dynlibs from core build system. I mean, if we place other stuff into Harbour dynlib, it's not Harbour dynlib anymore (the standard content, and interface is changed), but myharbour dynlib at best. AFAIK Lorenzo solves this by using hb-mkdyn.sh. The generic solution is pbly something to create dynlibs from each contribs/addons, or from a set of contribs/addons, named hbcontrib.so / hbaddon.so, where these dynlibs are not guaranteed to have any std interface. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
