Go to the FreeLists Home Page Home Signup Help Login
 



[openbeosnetteam] || [Date Prev] [08-2002 Date Index] [Date Next] || [Thread Prev] [08-2002 Thread Index] [Thread Next]

[openbeosnetteam] ELF linkage and libraries

  • From: "shatty" <shatty@xxxxxxxxxxxxx>
  • To: openbeosnetteam@xxxxxxxxxxxxx
  • Date: Sat, 24 Aug 2002 14:52:49 -0700
I just want to take this opportunity to point out that there
are a lot of programs that will try to link with -lsocket.
If it is possible to have an onmipresent link somehow between
libsocket.so and libnet.so it would simplify ports.
I still don't understand a lot about how libraries are
linked but is there perhaps a way to say that a
shared library depends on another? (within the lib)  In
this case you could make one of the libs simply depend
on the other and then have a nice breakdown of the
functionality between the API and libraries, without
forcing the app developer to list all those libs.

This extends to other libs too, like libc and libm.  It
would be rather clean if libbe would simply depend on 
a libc and libm rather than being a big ball of wax.

At the very least it would be helpful to have symlinks
from libc.so to libbe.so, (or libsocket.so to libnet.so)
if those links would work properly.  (I don't know 
about that question regarding the soname inside the libs.)

Andrew







[ Home | Signup | Help | Login | Archives | Lists ]

All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
Everything else ©2007 Avenir Technologies, LLC.