• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Linking in CW shared lib vs. Xcode framework
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Linking in CW shared lib vs. Xcode framework


  • Subject: Re: Linking in CW shared lib vs. Xcode framework
  • From: Jo Meder <email@hidden>
  • Date: Wed, 2 Aug 2006 14:04:38 +1200

Hi Fritz,

On 2/08/2006, at 11:24 AM, Fritz Anderson wrote:

There is a threshold issue here...

You're aware that Xcode can't produce CFM binaries?

Of course. I could have been clearer I guess, but I assumed most people would assume that the Xcode side of things was Mach-O. Too many assumptions, I apologise for that. I mentioned CFM because the app built with Codewarrior is CFM and not Mach-O ( which it could have been ), and I'm interested in the difference between what is happening with the CW/CFM shared lib and the Xcode/Mach-O framework. The reason the app is still CW/CFM after all this time is that we still support OS 9 for it. I'm now looking into building a Universal version for those with Intel machines, because our next product, which is already Universal, has been delayed.


Anyway, I'm even more interested to know now, because I have come across the same problem in another shared library I'm converting, and this time I don't think there is any way to restructure the code without things turning into a major effort, which may unfortunately prove to be the tipping point as to whether I finish updating this application.

With my app a certain system is split between the app and the shared library. This is because part of the system needs access to items in the app. I don't believe there is any part of the system in the shared library that tries to call functions in the app part directly, but I'm not really sure, most of this stuff has been working for about 6 years without problems and I can't remember all the details just now.

I'm really interested to know why the CFM version links and works fine, but the Mach-O version doesn't link. I think there are headers brought in which relate to source files which are only part of app, but why isn't this a problem with the CFM shared library ? Can I get similar behaviour with the Mach-O build ?

If anyone has any insight, I would really appreciate hearing it. Sorry if I'm not very clear about what I'm describing, I don't fully understand the behaviour of CFM in this situation so it's hard for me to be more explicit.

Regards,

Jo

--
Jo Meder
Planetside Software
email@hidden

Terragen for Macintosh
Photorealistic landscapes on your Mac
<http://www.planetside.co.uk/terragen/mac/>

_______________________________________________
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


  • Follow-Ups:
    • Re: Linking in CW shared lib vs. Xcode framework
      • From: Syd Polk <email@hidden>
  • Prev by Date: RE: Problems with hdiutil
  • Next by Date: Re: Problems with hdiutil
  • Previous by thread: Re: stop new header from being added to copy files?
  • Next by thread: Re: Linking in CW shared lib vs. Xcode framework
  • Index(es):
    • Date
    • Thread