Re: zero-link vs library
Re: zero-link vs library
- Subject: Re: zero-link vs library
- From: Simeon Leifer <email@hidden>
- Date: Thu, 20 Nov 2003 09:33:01 -0800
Makes sense, though I think I am within those bounds. Some more
information about my setup.
The libValidate.a library file is in my source directory along with all
my .m/.h and .nib (in English.lproj) files. I'm doing development
builds to a build directory that is in my source directory (default
XCode setup?). I start the app either via Build and Run or Build and
Debug. Shouldn't this be a valid scenario in which to use ZL?
libValidate.a is added to my project and marked as being a member of
the target I am building. I do not see it listed in any of the build
phases file lists, but i know it works right with ZL off. The
project/target is an xcode native cocoa application.
On Nov 20, 2003, at 9:00 AM, George Warner wrote:
On Wed, 19 Nov 2003 17:15:52 -0800, Simeon Leifer
<email@hidden> wrote:
I have several projects that use libValidate.a (though the specific
library is not at issue i imagine). When zero-link is enabled, the
application can not see any symbols from the library. Is this a bug,
known or not, and is there any way around it (short of disabling
zero-link which is a great time saver)?
Zero-link depends on files in your build directory to do everything
that it
does. If you move (or copy) your app to a different location then ZL
can't
find those files and fails. The moral of this story is to only use ZL
for
development (from the build directory) and use deployment to build
click-able apps.
--
Enjoy,
George Warner,
Schizophrenic Optimization Scientists
Apple Developer Technical Support (DTS)
_______________________________________________
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.