From: Godmar Back (gback@marker.cs.utah.edu)
Date: Fri Jan 08 1999 - 03:36:25 EST
I have another question about libtool:
>
> > What about architectures that don't have a libltdl port?
>
> libltdl currently supports the following dlopening mechanisms: dlopen,
> shl_load, GNU DLD and Windows' LoadLibrary. Additionally, it supports
> dlopening simulation for platforms that lack shared libraries (or have
> shared libraries disabled) through the dlpreopen mechanism, in which a
> symbol table is created when the program is linked and it -dlopens a
> set of libraries. If any of these libraries is static, libtool will
> link the library into the program and add its symbols to the
> dlpreopening symbol table. It's that simple.
>
Isn't that a waste of memory, potentially?
Since libtool cannot know which external symbols will actually be
referred to, it will have no choice but to include all symbols into this
dlpreopening table.
It appears that this requires programmers to be very careful about
avoiding global symbols whenever possible. Or is there a #pragma
or something that allows programmers to tell the tool chain to not
include a symbol in this table?
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:32 EDT