• 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: Specify multi-variant/arch output in custom build rule
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Specify multi-variant/arch output in custom build rule


  • Subject: Re: Specify multi-variant/arch output in custom build rule
  • From: Eric Albert <email@hidden>
  • Date: Wed, 3 May 2006 15:26:29 -0700

On May 3, 2006, at 1:09 PM, Jonas Maebe wrote:

On 3 mei 2006, at 21:27, Eric Albert wrote:

XCode then assembles it (using an internal build rule) using this command line:

/usr/bin/gcc-4.0 -x assembler -arch ppc -pipe -Wno-trigraphs - fpascal-strings -fasm-blocks -g -O0 -Wreturn-type -Wunused- variable -fmessage-length=0 -mtune=G5 -fvisibility=hidden -mfix- and-continue -mmacosx-version-min=10.4 -I/Users/jonas/elishome/ aop/build/Javana.build/Debug/Javana.build/Javana.hmap -F/Users/ jonas/elishome/aop/build/Debug -I/Users/jonas/elishome/aop/build/ Debug/include -I/Users/jonas/elishome/aop/build/Javana.build/ Debug/Javana.build/DerivedSources -isysroot /Developer/SDKs/ MacOSX10.4u.sdk -c /Users/jonas/elishome/aop/build/Javana.build/ Debug/Javana.build/DerivedSources/backends.s -o /Users/jonas/ elishome/aop/build/Javana.build/Debug/Javana.build/Objects-normal/ ppc/backends.o
backends.pp:1889:FATAL:Symbol BACKENDS_TBACKEND_$__CREATE $ANSISTRING$$TBACKEND already defined.


That symbol is the first global procedure symbol in the assembler code, and line 1889 of the assembler file is the start of the i386 assembler version of that function. So my "#ifdef __i386__" doesn't seem to have any effect. Is there a way to solve this with one or other #ifdef?

What you've shown should work. We do this a lot. Can you narrow this down to a single-file test case that I could try?

As noted in my other mail, the "-x assembler" is the culprit. Is there maybe some sort of CUSTOM_ASSEMBLER_FLAGS setting which I can modify to add "-x assembler-with-cpp" to that command? (before the input file, since it doesn't have any effect when it comes after an assembler file, but after the "-x assembler" switch, since they override each other)

I would've expected Xcode to pass -x assembler-with-cpp by default. I'm surprised it doesn't, since I can't think of a reason not to. Can you write up a bug on that?


Thanks,
Eric

_______________________________________________
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: Specify multi-variant/arch output in custom build rule
      • From: Jonas Maebe <email@hidden>
References: 
 >Re: Specify multi-variant/arch output in custom build rule (From: Jonas Maebe <email@hidden>)
 >Re: Specify multi-variant/arch output in custom build rule (From: Eric Albert <email@hidden>)
 >Re: Specify multi-variant/arch output in custom build rule (From: Jonas Maebe <email@hidden>)

  • Prev by Date: Re: [Q] is there any good replacement for the Xcode?
  • Next by Date: Re: XCode Resource Files
  • Previous by thread: Re: Specify multi-variant/arch output in custom build rule
  • Next by thread: Re: Specify multi-variant/arch output in custom build rule
  • Index(es):
    • Date
    • Thread