Re: gnulib & modules

Daniel Jour <[email protected]>
Newsgroups gmane.lisp.clisp.devel
Message-ID <CACZHyTM=0O7FVMvxb9_OW_3Eh0seVvtko4Yp1n6_WL8CGZxLgQ@mail.gmail.com>
> I think you are forgetting that the default is now dynamic_modules.

Even then, linking (as in producing) lib-module.so (why the non-standard
naming scheme btw?) could be done by resolving symbols with libgnu.a first.

E.g.:

When foo.o and bar.o are the CLISP module's object files, then

ld -r -o module.o foo.o bar.o libgnu.a

resolves gnulib dependencies from these two object files (and the
dependencies between them) and gives us a module.o that we can easily
convert into a shared library (without having to worry about gnulib
anymore).

------------------------------------------------------------------------------
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.