[openbeos] Re: Dynamically linked library inter-dependencies
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Mon, 15 Jul 2002 03:24:09 CEST (+0200)
Andrew wrote:
> Okay, I just got an email from a libtool developer who
> has cleared things up for me somewhat. Here's what you
> can not do on BeOS:
>
> 1. Create a "framework" (per Design Patterns) that uses undefined
> symbols.
> 2. Make it into a shared library.
> 3. Create an application that implements the framework.
> 4. Link the application code to the shared library.
> 5. Run the resulting application.
>
> This is possible on some platforms. There may be some
> issues with steps 4 & 5. I don't know, because on BeOS
> you can't get past step 2.
>
> I don't know what platforms in particular allow you to
> do this but I have a strong suspicion that linux is one
> of them. Some platforms which support dlopen probably
> also support this.
No, BeOS is able to do that, it just handles it a bit differently.
Basically, you link your shared lib against a dummy _APP_. Since BeOS
uses _APP_ as the .so-name, you can just use this shared library in any
application that resolves all undefined symbols of the library.
Adios...
Axel.
Other related posts:
