Re: ZeroLink and Fix and Continue failure
Re: ZeroLink and Fix and Continue failure
- Subject: Re: ZeroLink and Fix and Continue failure
- From: Jonathan Hess <email@hidden>
- Date: Wed, 19 Oct 2005 10:01:13 -0700
On Oct 18, 2005, at 12:19 PM, James Bucanek wrote:
I suspect that the majority of ZeroLink problems, and possibly the
cause of your problem, is an attempt to call a ZeroLink-resolved
function very early in your application -- before the ZeroLink
facility has been, or can be, initialized.
I read the associated caveats on ZeroLink and, with the static
initializer scheme I'm using, hoping it still isn't a real problem (I
could be wrong).
The particular trick I'm doing is the same as line 76 in the iostream
header:
static ios_base::Init __ioinit;
So... if someone else could confirm that ZeroLink does or doesn't
work with applications that use iostreams (ie cout)?
The other issue could be your subversion of the linker by
specifying the statically linked libraries using command-line
arguments rather than having them as input files to the Linker
phase. It's entirely possible that ZeroLink no longer knows about
your libraries, and has no linkage to them at all.
Have any suggestions on a better way to get static linking? When I
add the .a's to the xCode project (to me this should indicate I want
static linking or I would have dragged the dylib's or .so's). I
don't want to have to install pcre, png, antlr, and etc in /usr/lib
on target machines. Hmmm... maybe I should read up to see if there's
a way to have the dynamic libraries local to my app bundle. But, I'm
trying to reduce differences between platforms for this cross
platform monster.
, Jonathan Hess
_______________________________________________
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