On Saturday 25 June 2011 13:52:02 Alexandre Ratchov wrote:
> There's code (eg. audio/openal, but not only) that does:
>
> dlopen("libsndio.so", ...);
>
> and then calls dlsym() for each function and so on. What's the point
> of doing this instead of simply linking the binary with -lsndio and
> using functions normally?
>
> hints?
>
> -- Alexandre
Extending the same subject a little: I'm interested in knowing how to handle
these with ports? Is there a real good rule of thumb here and is this
documented in the ports faq?
For example xvidcore adds some libs to WANTLIB even though check-lib-depends
doesn't want them. But devel/sdl depends on libGL that it opens with dlopen()
and there is no "GL" in WANTLIB.
--
Antti Harri
