Re: Debug Configuration Linking
Re: Debug Configuration Linking
- Subject: Re: Debug Configuration Linking
- From: email@hidden
- Date: Sun, 18 Jun 2006 13:10:04 -0400
On 18 Jun 2006, at 2:38 AM, email@hidden wrote:
1) I have a static library that I compiled from source (the
Irrlicht engine library); naturally, I compiled this library using
the Release Configuration.
When I compile my program using the Debug Configuration and then
link against this library, I get the following error:
/usr/bin/ld: /Path/To/IrrlichtLibrary.a(png.o) has local
relocation entries in non-writable section (__TEXT,__text)
collect2: ld returned 1 exit status
However, when I compile my program using the Release Configuration,
the linking succeeds, and the program runs.
2) Then I compiled the Irrlicht library using the Debug
Configuration. Then my program compiled, linked, and ran using
either of the Debug or Release Configuration.
Thus, the Debug Configuration of my program doesn't like something
about the Release Configuration used to build the Irrlicht library.
How can I use a Release Configuration library and still debug my
program?
Thanks.
So, I figure that I need two versions of the library; one for
debugging and one for release.
Is this the case?
Are Apple's Frameworks built with a debugging configuration?
I can't imagine that this is the case for a number of reasons, but I
also make use of the GMP library, which I have compiled as a dylib
via the command line.
This gives me no trouble.
Are only static libraries affected?
Thanks.
_______________________________________________
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