I tried "file libfreeimage.dylib" and "lipo -info libfreeimage.dylib"
and they both said it is of x86_64--no mention of i386. I guess I
will have to try it on some other ports to know whether this happens
for all ports.
I still do not understand why I get warning messages about foo.dylib
when I am linking to foo.a. Can anyone explain this to me?
Thanks,
Paul
On Sep 9, 2009, at 3:11 PM, Ryan Schmidt wrote:
On Sep 9, 2009, at 15:10, Paul Dennis Simonson wrote:
Thanks for the tip. I tried using
sudo port upgrade --enforce-variants freeimage +universal
and it seemed to compile just fine. I then went back to XCode and
added the i386 architecture (in addition to x86_64). I compiled
and still got a warning (and error messages) saying that
libfreeimage.dylib (again, I was trying to link to libfreeimage.a)
was of the wrong architecture. This seems to indicate to me that
it did not in fact build the i386. When I try to just use the
x86_64 architecture in XCode, it builds just fine. I have not
tested it on other ports.
"lipo -info" should be able to tell you what architecture
libfreeimage.dylib is.
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
