Extra Junk in Library
Extra Junk in Library
- Subject: Extra Junk in Library
- From: Dave Keck <email@hidden>
- Date: Mon, 26 Jul 2004 22:25:01 -0400
Hello,
Lately I've been creating several static and dynamic libraries using
Xcode. Somewhere along the line I noticed Xcode is putting junk (such
as paths to my build directory) in the final library. I have activated
the "Deployment" target and have played around with different settings,
but I can't seem to get this junk out of the library when compiling
with Xcode.
Xcode must be feeding gcc some flags that promote this operation. Does
anyone know what flags might do this?
I'm using gcc 3.3 and Xcode 1.2.
For an example of what I'm talking about, do the following:
1. Open Xcode and create a new project of type "BSD Dynamic Library".
It doesn't matter what type of project you make as long as it's some
type of library.
2. Set the target to "Deployment".
3. Compile the library (it doesn't matter that there isn't any code).
Now open the library in TextEdit. Look towards the bottom. You should
see the full path to the project's directory.
It doesn't make any sense that Xcode (well, gcc) is putting this junk
into the library, as the library doesn't need it to be used.
Does anyone know how to get rid of this junk in the library? (As far as
I can tell, it doesn't affect applications, bundles, etc. - only
libraries. And it's very possible to make a library using the
command-line that doesn't contain this unnecessary information.)
Thanks for any insight!
Dave
_______________________________________________
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.