[lug] q: building libraries

[Chan Kar Heng]

hi.

<all the "good stuff" (tm) previously snipped>

sorry for being off topic again.. just 1 more follow up question.

having these .so shared objects created, must it only
be located in a directory that's looked at
by ldconfig? u know... like in winblows, the .dll file
could be in the same directory as the executable or in
c:\windows or c:\windows\system or c:\windows\system32.
like if i just want the library to be used by one app,
not all. possible?

i recall very briefly reading about functions in C that
could allow one to open some kind of compiled code and
use functions in them... i can't seem to find them anymore.
anyone have any idea on these? the examples i saw, it
was as if the function could be used to specify a library
file name, load functions out of it and use them...
i guess the way it works, it may somewhat be similar to
kernel modules or app plug-ins.

just a side note for those who aren't so much of an anti-windows.
the recent version of cygwin has -shared option supported!
though there're still problems with this early release
that're being addressed.

as for dlltool, the version i saw existed on cygwin. and yep,
for building dlls. don't know how the linux version works though.




--------------------------------------------
i don't suffer from stress... i'm a carrier.