Re: [AD] Is this a misconfiguration on OS X?

[Elias Pschernig <elias.pschernig@xxxxxxxxxx>]

On Sat, 2010-02-13 at 01:06 -0500, Kibiz0r wrote:
> I found this because I can't seem to use Mono's P/Invoke to call into
> A5 on OS X.
> 
> Compare this output...
>
> otool -L /usr/local/lib/liballegro-4.9.16.dylib 
> /usr/local/lib/liballegro-4.9.16.dylib:
> liballegro-4.9.16.dylib (compatibility version 0.0.0, current version
> 0.0.0)
...
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
> version 125.0.0)
> 
> 
> ...to that of A4...
> 
> 
> otool -L /opt/local/lib/liballeg.dylib 
> /opt/local/lib/liballeg.dylib:
> /opt/local/liballeg-4.2.dylib (compatibility version 4.2.0, current
> version 4.2.3)
...
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
> version 125.0.0)
> 
> 
> From my limited knowledge of dylibs, I believe the first line is
> supposed to be self-referential, but using an absolute path.

Isn't that what it's doing in both cases?

> My assumption is that this is not a problem for normal C usage,
> because dyld will fall back to /usr/local/lib anyway, but the
> inconsistency -- along with the reported version numbers being 0.0.0
> -- suggests a potential source of trouble.

Yes, we need to fix this, but it's easy, just two values to fill into
CMakeLists.txt somewhere. Did you compile Allegro with "make" or with
"xcodebuild"? (Not sure it makes a difference.)


-- 
Elias Pschernig <elias.pschernig@xxxxxxxxxx>