• 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: -fasm-blocks not working properly for ppc in Xcode 3.2?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: -fasm-blocks not working properly for ppc in Xcode 3.2?


  • Subject: Re: -fasm-blocks not working properly for ppc in Xcode 3.2?
  • From: Jim Wintermyre <email@hidden>
  • Date: Mon, 31 Aug 2009 22:38:47 -0700

At 9:54 PM -0700 8/31/09, Michael Dautermann wrote:
On Aug 31, 2009, at 7:33 PM, Jim Wintermyre wrote:


Hi Jim,


I had a similar problem like this with a project I'm working on, when I moved up to Snow Leopard + XCode 3.2.


Make sure your assembly flags include a "-fmacho" format specifier and see if that does the trick.


Thanks for the reply - sorry for the dumb question but how exactly do I set that?


Thanks,
Jim


I'm not looking at my project file at the moment (they're held hostage at the office, paranoid bosses being what they are ;-), but if the inline assembly is being compiled using nasm then I believe there's a user-defined setting (or flag) you can add to the target in XCode to get the "-fmacho" option passed in when nasm is called (do a "man nasm" at the command line to see the various options).


Or, you might not be using nasm to compile the inline assembly. It might be useful to print out the errors being thrown in the Build Results window, along with the actual commands (i.e. which compiler / tool / etc. was throwing the error) that generated that error. That way, we'd know for sure whether it was nasm or CompileC or something else.

I'm not using nasm, it's just a couple lines of inline assembly in a C++ file. It seems pretty clear from the debug output that the problem is just that -fasm-blocks is not getting passed to gcc even though "CodeWarrior-Style Inline Assembly" is checked (this caused -fasm-blocks to get passed to gcc in previous versions of Xcode). Manually specifying -fasm-blocks in the "Other C Flags" setting does work though.


Jim
_______________________________________________
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


References: 
 >-fasm-blocks not working properly for ppc in Xcode 3.2? (From: Jim Wintermyre <email@hidden>)
 >Re: -fasm-blocks not working properly for ppc in Xcode 3.2? (From: Michael Dautermann <email@hidden>)
 >Re: -fasm-blocks not working properly for ppc in Xcode 3.2? (From: Jim Wintermyre <email@hidden>)
 >Re: -fasm-blocks not working properly for ppc in Xcode 3.2? (From: Michael Dautermann <email@hidden>)

  • Prev by Date: Re: -fasm-blocks not working properly for ppc in Xcode 3.2?
  • Next by Date: 10.5.8 Debug Library Framework: App crash on launch: No "CarbonCore"
  • Previous by thread: Re: -fasm-blocks not working properly for ppc in Xcode 3.2?
  • Next by thread: Re: -fasm-blocks not working properly for ppc in Xcode 3.2?
  • Index(es):
    • Date
    • Thread