From: Stefan S. <se...@sy...> - 2004-09-02 02:43:56
|
Grzegorz Jakacki wrote: > Majority of my time invested in 2.8 release went into > solving problems related to libgc, libltdl, libtool, > autoconf/automake (in this order). > > I suggest to minimize impact of these technologies > on OpenC++ Core Lib, so that we can focus on templates > and overloading, and not on dynamic linking. I totally agree. I may be missing something but I don't understand the usefulness of running occ to build a plugin in one run, loading and using it in a second run. Is anybody actually using such a procedure ? What is its purpose ? Once we get of dynamic loading we can elimiate libltdl. In synopsis I use a stripped-down build system using make and autoconf (i.e. no automake and no libtool !). The windows version is compiled using 'gcc --mno-cygwin', which is equivalent to mingw. I anticipate to move to scons (http://www.scons.org) in the not-so-distant future. That will simplify matters even further, especially concerning portability. As far as libgc is concerned, I'm eliminating GC from all but the ptree types, as in all other cases ownership is well defined and can be dealt with by other means (pass-by-value, for example, for Encodings). We may consider ref counting in some cases, too. Just some ideas... Regards, Stefan |