Re: Incompatibilities between home-compiled and apple's libpng
Re: Incompatibilities between home-compiled and apple's libpng
- Subject: Re: Incompatibilities between home-compiled and apple's libpng
- From: Damien Bobillot <email@hidden>
- Date: Tue, 11 Oct 2005 12:09:35 +0200
Peter O'Gorman wrote :
D. Walsh wrote:
This doesn't work by mistake, it works because you are repackaging
a static library as a dynamic library and providing the current
and compatibility information.
There already was a dynamic shared library with the correct current
and compatibility versions though, making up different numbers to
solve the problem is not right, I feel.
The existing library with the same name cannot be used, because it
does not export the same symbols. So I MUST compile my own version of
the libpng.
Meanwhile, I've found an obvious solution to my problem : just adding
the static lib libpng.a to my project... (300Ko is not so much).
The real issue is that Apple uses the opensource libpng library, but
don't export the png_* symbols. So it's impossible to use this
library in our programs without any hacks. Why Apple don't
make it publicly available ? (may be off topic...)
Anyway, I think the original poster has DYLD_LIBRARY_PATH set
somewhere to be getting this behavior.
I do. However, if I put my library in /usr/lib, I don't need
DYLD_LIBRARY_PATH anymore. So my problem has nothing to do with
DYLD_LIBRARY_PATH.
--
Damien Bobillot
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden