Behavior when Host and Plugin link to different SDKS? Was: Resolving conflicting typedefs uint32
Behavior when Host and Plugin link to different SDKS? Was: Resolving conflicting typedefs uint32
- Subject: Behavior when Host and Plugin link to different SDKS? Was: Resolving conflicting typedefs uint32
- From: Thomas Engelmeier <email@hidden>
- Date: Sat, 19 Jul 2008 12:56:56 +0200
Am 15.07.2008 um 08:11 schrieb email@hidden:
I'm trying to convert a Quark XTension from Tiger to Leopard but am
getting a conflicting typedef error for uint32
/Volumes/PageManager Dev/PageManager XT/../XTHeaders/XP_XTplatE7.h:
244: error: conflicting declaration 'typedef long unsigned int uint32'
/Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/
Security.framework/Headers/cssmconfig.h:64: error: 'uint32' has a
previous declaration as 'typedef uint32_t uint32'
Depending on the SDK, frameworks can have different behaviors - I
spent quite some of yesterdays time working around some unwanted
NSNumber behavior when linked against the 10.4 SDK and running on
Leopard (vs. linking against the 10.5 SDK)
I wonder what happens in the case of Plug-In architectures.
- how does the magic behind the scenes work? I'd expect Xcode to
link against the unresolved "Current" version symlink of a Framework,
is that right? Then how does the bugfix behavior work? Or does Xcode
resolve the symlink and links against that variant ( Versions/C/
Whatever )?
- What happens when there is an SDK mismatch between Plug-In and and
Host?
a.) each one gets the appropriate SDK implementation - what
happens to objects traversing binary bounds? I. e. a NSNumber in the
host (10.4 SDK) with the "undesired" behavior passed on to the plugin
(fixed behavior)
b.) The host mandates the SDK implementation used - how? What
happens to new introduced APIs un the newer SDK?
TIA,
Tom_E
_______________________________________________
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