-gfull + dead cod stripping
-gfull + dead cod stripping
- Subject: -gfull + dead cod stripping
- From: Marc Poirier <email@hidden>
- Date: Mon, 16 Aug 2004 14:27:09 -0400
I was just reading:
http://developer.apple.com/documentation/DeveloperTools/Conceptual/
Build_System/Dead_Code_Stripping/DeadCodeStripping.html
which says:
You must recompile all object files using the compiler included with
Xcode 1.5 before dead-code stripping can be performed by the linker.
You must also compile the object files with the -gfull option to ensure
that the resulting binaries can be properly debugged. In Xcode, add the
-gfull option to the Other C Flags build setting of your target.
Note: The GCC compilers -g option normally defaults to -gused, which
reduces the size of .o files at the expense of symbol information.
Although the -gfull option does create larger .o files, it often leads
to smaller executable files, even without dead-code stripping enabled.
So does that mean that I should use -gfull even on Deployment builds,
or only on Development (debug) builds?
Oh and also, right before that, it says: "In Xcode, use the Dead Code
Stripping and Dont Dead-Strip Inits and Terms build settings,
respectively." Does that mean that I would only use the "Inits And
Terms" setting if I already have "Dead Code Stripping" enabled, or does
it mean that if I use one I always have to use the other, otherwise
things won't work right?
thanks,
Marc
_______________________________________________
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.