linking against Universal libcrypto
linking against Universal libcrypto
- Subject: linking against Universal libcrypto
- From: "John C. Daub" <email@hidden>
- Date: Tue, 17 Jan 2006 13:54:29 -0600
- Thread-topic: linking against Universal libcrypto
Hello.
We have a project that links against libcrypto. In the past, the way we did
it was to just add
"-lcrypto"
to our "other linker flags" setting. And it worked just fine.
A co-worker (using Xcode 2.2) is now trying to get this project outputting
an Intel binary, and it failed to link. He didn't tell me the exact error,
but it was because the libcrypto that was being linked had no Intel code in
it.
When I looked on my PPC machine running OS 10.4.4 in /usr/lib, using "lipo
-info" on the libcrypto in there, it said it was a PPC-only binary. When I
looked at the libcrypto within my 10.4u SDK, that's a universal binary.
We added another linker option: "-L$SDKROOT/usr/lib" and that made things
work... we were able to link our Intel build. So it seems that before
setting -L, our -l option was looking for the libcrypto on the system in
/usr/lib and not at the SDK. Again, this is a co-worker doing this, so I
don't have the full build output.
Is this expected behavior? When specifying a link option like -l, shouldn't
it honor the SDK setting and not be looking in the system?
Thank you.
--
John C. Daub }:-)>=
<mailto:email@hidden> <http://www.hsoi.com/>
"We are what we repeatedly do." - Aristotle
_______________________________________________
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