wchar link problem - kinda sorted, i think.
wchar link problem - kinda sorted, i think.
- Subject: wchar link problem - kinda sorted, i think.
- From: joshua portway <email@hidden>
- Date: Mon, 27 Oct 2003 01:28:19 +0000
hmm.
I think I've found the problem - as well as the "deployment target"
setting in the target info window, there's a target SDK setting in the
general prefs for the whole project, which I hadn't seen before so it
had been set to "current MacOS".
Now I've set it to 10.1.5, however and the project won't even compile.
As soon as it tries to include the STL <string> header it falls over
with all sorts of compile errors.
I guess this is because I'm using GCC 3.3, and i need to use GCC 3.1 in
order to build for 10.1.5 - is that right ? If so, that means I'll lose
all of the GCC 3.3 loveliness, like faster code and faster build times.
Losing the faster build times will really hurt, because our project has
thousands of files and used to take over 4 hours to build before gcc3.3
and distributed builds.
The thing is that I'm a bit loathe to abandon GCC 3.3 just because of
this one problem with one bit of the project. If I split this plugin
into a separate project and build only that with GCC3.1 will that work
? I know there are incompatibilities between binary code built using
different versions of GCC , but can I load a plugin built with GCC 3.1
into an app built with 3.3 ?
josh
_______________________________________________
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.