• 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: Native targets always build with debug settings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Native targets always build with debug settings


  • Subject: Re: Native targets always build with debug settings
  • From: Dario Accornero <email@hidden>
  • Date: Fri, 7 Nov 2003 17:17:44 +0100

On 4 Nov 2003, at 2:57, Monroe Williams wrote:

On Nov 3, 2003, at 4:23 PM, paul wrote:

I've been working on this for a few days, but haven't been able to figure this.
In Xcode 1.0, any native target always builds with optimization = size, debugsymbols = on.


My pb imported targets respect my deployment settings of -O3, and no debug symbols,
but as soon as I convert the target to native, all that goes out the window.


I have tried creating new xcode projects, same thing; native targets always build as a debug target.
I have set the target and the style to remove all zero-link, fix-continue, debug symbols, optimization=size settings I can find.
I have not yet gone so far as to edit the pbproj file directly, but a dump shows that all debug type options are set to NO.


so, I'm out of ideas, unless this is a bug or known issue, I cannot get a native target to compile w/ out debug symbols. This is very important to me, as my app is 60mb with debug symbols on, and 5 mb with them off.

I'm in the same boat (although the sizes are 42MB and 2.5MB in my case). Since this happens even in empty projects created from scratch, I wonder how other people are compiling *without* debug symbols and *with* optimizations...


I don't know how to solve the problem inside XCode, but you can work around it post-build by running 'strip' on your binary from the command line. I'm doing this from an external shell script I use to build a disk image for distribution and it works great. If you want to keep just enough debug info for crash log backtraces to show function names, use 'strip -S' instead of just 'strip'.

You could even do this from a shell script phase that happens after your link if you want to automate it.

...except that if you add a shell script phase in Xcode 1.0 the script is not executed when it should (known and reported issue).


Dario
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

References: 
 >Native targets always build with debug settings (From: paul <email@hidden>)
 >Re: Native targets always build with debug settings (From: Monroe Williams <email@hidden>)

  • Prev by Date: Adding a sourcecode filetype
  • Next by Date: Inclue paths, was: Boost and frameworks
  • Previous by thread: Re: Native targets always build with debug settings
  • Next by thread: Java Namespaces
  • Index(es):
    • Date
    • Thread