FreeLists / openbeosnetteam / [openbeosnetteam] Re: libnet fix

["Marcus Overhagen" <ml@xxxxxxxxxxxx>]

Daniel Reinhold wrote:

> point of view, trying to actively develop a lib with the SAME NAME and 
> the EXACT SAME SET OF EXPORTED SYMBOLS as a standard existing lib (and 
> being loaded from the same set of standard search paths) is just asking 
> for brain frying troubles.

Oh well, it isn't really a problem if you know where to put the library.

Assuming you want to execute /boot/foobar/testapp, and this app 
needs libnet.so the BeOS loader will search the library in this order:

1. /boot/foobar/lib/libnet.so
2. /boot/home/config/lib/libnet.so
3. /boot/beos/system/lib/libnet.so

using the same library name works very well for media kit
testing, where I just place a link to our media kit library in the distro dir
into /boot/home/config/lib/

> Why not use 'libobosnet.so'? Or something distinctive. You can *always*
You can't run normal R5 programs.

> change it to the standard name later, once the thing has matured, and 
> test against that. In the mean time, sanity is preserved. Is this 
You can do that, if you need it. but the need to do it is very low.

However, this linker bug(?) should be investigated. it is really crazy that 
we can't link a library from object files that has a symbol called _res.

> absolutely necessary? No. But isn't it worth keeping things straight 
> and not spending hours (days) tracking down non-existent problems 
> because of linking against the wrong lib?
We are not linking against the wrong lib.

Whenever the name "libnet.so" (or "libmedia.so") is used in the jamfile,
we will link against our new library, while using the name "net" or "media"
will link to the R5 files.

The jamfiles for route, ping, etc. are correct and link against the new file.

> Just a kooky suggestion.
Yes, we (you) can rename to libobosnet.so', but I don't believe that this is 
very
useful workaround to solve this bug (renaming _res is only a workaround, too)

Marcus