|
From: Christophe Prud'h. <pru...@MI...> - 2000-08-13 01:27:49
|
> The first thing I realized is that to enable dynamic loading I need to
> add the /usr/lib/libdl.a to the link line. Ipso facto it stands to
> reason that if I integrate this work to libcorelinux we end up with a
> dependency in the core we didn't normally have.
libdl.a is standard, so requiring it is not such an issue
what we can do is update the corelinux configure.in to enable -ldl for the
examples
and update the AC_CHECK_CORELINUX for users who want to useconf+corelinux
and document for all other users
>
> What I'm getting at is I think that the IMPLEMENTATION of frameworks, in
> this case the FunctionalLibrary loader et.al. are probably really an
> example of the CoreLinux++ frameworks that are one of the goals of the
> project.
>
> Anyone?
so what you say is that it is time to putthings into libframeworks?
if so why not!
in fact it is quite good to think that core(linux) really means it (that it
is a core library): that is to say that it doesn't extra libs
-ldl is not such a requirement but keeping corelinux as a standalone lib(a
part the c++ lib of course) is very good since dl features are needed only
for a one corelinux feature
My preference would be to not add -ldl as a requirement and so begin to
populate corelinux++ frameworks
C.
--
Christophe Prud'homme | So so is good, very good,
MIT, 77, Mass Ave, Rm 3-243 | very excellent good:
Cambridge MA 02139 | and yet it is not;
Tel (Office) : (00 1) (617) 253 0229 | it is but so so.
Fax (Office) : (00 1) (617) 258 8559 | -- William Shakespeare,
http://augustine.mit.edu/~prudhomm | "As You Like It"
Following the hacker spirit
|