[openbeosnetteam] Re: ELF linkage and libraries
- From: "Philippe Houdoin" <philippe.houdoin@xxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Mon, 26 Aug 2002 22:18:15 +0200 (added by postmaster@wanadoo.fr)
BGA wrote:
> What exactky do you mean? libnet constains the C++ API and libsocket
is
> the standard sockets API. Also,
Hum, no.
Under a R5, we have these libraries:
libnet.so (BSD socket + BIND C API)
libnetapi.so (C++ BNet* classes, specific to BeOS, linked against
libnet.so)
Under a R5 + BONE, you still have the two before, plus these ones:
libsocket.so (BSD socket C API)
libbind.so (BIND C API)
libbnetapi.so (C++ BNet* classes, specific to BeOS, linked against
libsocket.so)
See the double 'b' in libbnetapi.so, right?
As some structs and consts in R5 libnet.so are not POSIX compliant,
Howard choose to
separate completly the BONE libraries and R5 net_server ones to make
them
coexists.
We choose another way to handle this: dynamicly detect if the app
expect the
R5 net_server's libnet compatibility or POSIX compatibilty (so BONE
apps, too).
-Philippe
--
Fortune Cookie Says:
The more things change, the more they stay insane.
Other related posts: