The default architecture setting for the release build is "ppc i386",
but it's "i386" for the debug build. Now the release build of my
application seems to work fine.
Why would the debug build crash using the same code and dylibs?
I gathered more fyi information:
graham-reitzs-macbook-pro:mysql grahamreitz$ file libmysqlclient_r.
libmysqlclient_r.15.0.0.dylib: Mach-O dynamically linked shared
graham-reitzs-macbook-pro:lib grahamreitz$ file libmysqlpp.2.3.2.dylib
libmysqlpp.2.3.2.dylib: Mach-O dynamically linked shared library i386
On Dec 1, 2007, at 11:08 AM, Graham Reitz wrote:
> libmysqlclient_r.15.0.0.dylib ---> Kind: Mach-O dynamic library. I
> don't see anything about architecture in Get Info
> libmysqlpp.2.3.2.dylib ---> Kind: Mach-O dynamic library. I don't
> see anything about architecture in Get Info
> I will also ask this question on the Xcode users list.
> If I can figure out which architecture these are built for I should
> be able to match it up in my project settings. Do you think this
> could cause the strange seg. fault behavior I see in debug mode?
> It's weird that it doesn't complain about architecture in debug mode.
> I am probably missing something.
> Also, how do I go about building the mysql++ debug and static
> libraries? Are there switches in the config script for that?
> Thanks again for your help.
> On Dec 1, 2007, at 12:48 AM, Warren Young wrote:
>> Graham Reitz wrote:
>>> ld: warning in /sw/lib/mysql/libmysqlclient_r.dylib, file is not
>>> of required architecture
>> There are *four* architectures in a complete Universal binary under
>> Leopard, not two as in Tiger: PPC and x86, each in both 32-bit and
>> 64-bit flavors. You can see what flavors the .dylib file is built
>> for by doing a Get Info on it. I'll bet Fink isn't building all
>> four (probably only one, in fact), and your Xcode settings are set
>> for one of those missing alternatives.
>> MySQL++ Mailing List
>> For list archives: http://lists.mysql.com/plusplus
>> To unsubscribe: http://lists.mysql.com/plusplus?unsub=1