>> 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.
Maybe HB_CORE_ADDON_DIRS, HB_CORE_ADDON_LIBS could allow for such extensions but it still hits me as wrong to extend core like that as it pulls away from the idea of having standardized distributions which work the same way on all systems. [ Adding support in such way seems technically possible by modifying only 3-4 places in make system (src/Makefile, config/bin|dyn|lib.mk, but I didn't make tests. ] BTW quick scan tells me that injection of local RDDs to harbour.so wasn't possible even before today's removal of HB_DB_EXT* vars, at least support was far from complete. I didn't try it though, so it may have worked by accident. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
