Re: thin linking: "file is not of required architecture"
Re: thin linking: "file is not of required architecture"
- Subject: Re: thin linking: "file is not of required architecture"
- From: Steve Checkoway <email@hidden>
- Date: Mon, 21 Apr 2008 08:37:39 -0700
On Apr 21, 2008, at 8:01 AM, Philip Hölzenspies wrote:
With regards to the dylib/so discussion: I want to wash my hands of
it. Our compiler uses BSD conventions. I'm not quite sure on the
issue, but somehow I have this idea in the back of my mind that
dylib defaults to objective-c calling conventions. I actually
require ANSI-C calling conventions, because other stuff will be
linked against my libs.
I haven't been following this at all, but I have no idea what you mean
by bsd calling conventions vs. ansi-c calling conventions vs objective-
c calling conventions. A function call convention is generally
something that the hardware specifies. See <http://compilers.iecc.com/comparch/article/03-02-079
>.
The calling conventions for systems on which OS X is supported are
described in <http://developer.apple.com/documentation/DeveloperTools/Conceptual/LowLevelABI/Introduction.html
>.
Maybe you mean something else.
--
Steve Checkoway
"Anyone who says that the solution is to educate the users
hasn't ever met an actual user." -- Bruce Schneier
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