• 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: compiling a bundle on intel?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: compiling a bundle on intel?


  • Subject: Re: compiling a bundle on intel?
  • From: Jonathan deWerd <email@hidden>
  • Date: Sat, 9 Aug 2008 17:52:59 -0600


On Aug 9, 2008, at 5:22 PM, Bob Sabiston wrote:

Hi,

I have a Cocoa bundle that I compile with my Carbon program. I used the Apple examples to do it, and I don't have a very thorough understanding of Cocoa or bundles. However, on my G5 w/ Codewarrior compiling (still!), it actually works. I have to compile the bundle using Xcode, but the rest of the app I compile in Codewarrior, just including the bundle as a library.
Whoa, it's Bad Karma to mix binaries from two different compilers. It should work, but in my experience it's best to go with a single compiler for everything, be it codewarrior, gcc, gcc-llvm, or whatever the latest popular compiler happens to be. Good job getting it working thus far, and good luck for the future...

However, lately I am compiling the whole thing with Xcode on Intel machines,
Yay!

and today I noticed that my Cocoa Window won't load. I opened the separate little bundle project to try compiling an Intel version, and it opens but the 'Build and Go' button is greyed out. What would cause this? On the G5 I've got Xcode 2.41, whereas on the Intel I've got 3.1. What do I need to do to compile the bundle project on Intel?
Are both the build and the build-and-go buttons grayed out? If the build button still works (but not the 'go' button and hence not build +go), the problem is that you have xcode making a bunch of object files but you haven't defined how it should turn those into an executable. Probably the best way to do that would be to make a new carbon project, then import your code into it. Crude, but it's a quick fix if you don't want to mess with targets and custom executables.

If that isn't the problem, then try looking at the compilation settings and comparing them to Apple's examples.

If you *do* want to mess with targets and custom executables (or magically generated executables), IIRC there is some fairly extensive reading on those subjects in the xcode manual.



Thanks
Bob

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
@gmail.com


This email sent to email@hidden

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >compiling a bundle on intel? (From: Bob Sabiston <email@hidden>)

  • Prev by Date: Re: Custom URL Handling
  • Next by Date: Re: Custom URL Handling
  • Previous by thread: compiling a bundle on intel?
  • Next by thread: generating a moveRight
  • Index(es):
    • Date
    • Thread