Re: XCode 3.0 vs 3.1 linking
Re: XCode 3.0 vs 3.1 linking
- Subject: Re: XCode 3.0 vs 3.1 linking
- From: Rich Collyer <email@hidden>
- Date: Wed, 8 Oct 2008 15:49:31 -0700
As I understand it, the -mmacos_version_min is for setting the
Deployment Target of the application. Since the libcrypto
Configuration (as far as I can tell) only cares about the Deployment
processors (ppc, i386), how do I convince it to build for a Deployment
Target of 10.4 (as opposed to whatever it defaults to)?
Thank you for the pointer so far.
+++++++++++++++++++++++
Rich Collyer
Senior Software Engineer
IronKey, Inc.
email@hidden
+++++++++++++++++++++++
On Oct 8, 2008, at 3:09 PM, Peter O'Gorman wrote:
Rich Collyer wrote:
Why does XCode 3.1 complain about not understanding the symbols for
the
stdlib functions open, write, close, read, strerror, & fputs, while
XCode 3.0 is perfectly fine with them? What is missing in the
project
that 3.1 is expecting?
/Undefined symbols:/
/ "_open$UNIX2003", referenced from:/
/ _RAND_poll in libcrypto.a(rand_unix.o)/
Looks like your libcrypto.a was not built with the same
SDK/-mmacosx_version_min settings as your final output.
Peter
--
Peter O'Gorman
http://pogma.com
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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