Re: xcode-users digest, Vol 1 #41 - 21 msgs
Re: xcode-users digest, Vol 1 #41 - 21 msgs
- Subject: Re: xcode-users digest, Vol 1 #41 - 21 msgs
- From: Ian Clark <email@hidden>
- Date: Thu, 6 Nov 2003 11:13:19 +0000
On Wednesday, November 5, 2003, at 06:10 pm, Rob Barris wrote:
From: Brent Marykuca <email@hidden>
Subject: Re: wchar link problems building for jaguar
Date: Tue, 4 Nov 2003 15:57:12 -0800
On Oct 28, 2003, at 4:50 PM, Thane Norton wrote:
We seem to have a solution for building a 10.1.5 thru 10.3 binary
using
XCode and GCC 3.3. Can't claim it will work for everyone, but it got
our
stuff up and running.
I have a slightly different solution to this problem, which I posted
in
another thread "10.2 deployment issues".
In a nutshell, there seems to be a problem with the way Xcode sets up
include paths when you're doing cross-development builds, such that
some important C++ headers (notably c++config.h) are read from the
Panther /usr/include tree instead of the SDK's. You can fix this by
adding the following to your target's Header Search Paths build
settings:
/usr/include/gcc/darwin/3.3/c++
/usr/include/gcc/darwin/3.3/c++/ppc-darwin /usr/include/gcc/darwin/3.3
Our Xcode project has 49 targets (individually built static libs).
What's the shortest route to getting the right paths activated across
all the targets other than pasting the characters above into all of
them?
Can I set up some kind of global environment variable/value that can
then be referenced in all the targets?
Will a future Xcode release deal with this more cleanly (ie is it
considered a bug yet?)
I have a similar situation, but have in one project
5 Frameworks
2 Apps
2 Tools
25 or so plugins
What I'd like to see is user definable per target-type style settings
that are separate from build styles
eg. For each target, a TARGET_TYPE (which I can change and set my own
types, but defaults to the type in the New Target dialogue)
TARGET_TYPE = Framework
TARGET_TYPE = Application
TARGET_TYPE = Tool
TARGET_TYPE = Plugin
TARGET_TYPE = This Type of Plugin
TARGET_TYPE = That Type of Plugin
etc.
Then depending on the TARGET_TYPE, a number of settings similar to
build styles
Target Types
Framework
INSTALL_PATH = /Here
Application
INSTALL_PATH = /There
PREFIX_HEADER = ApplicationPrefix.h
Plugin
INSTALL_PATH = /Library/myApp/Plugins
PREFIX_HEADER = PluginPrefix.h
These are settings that wouldn't usually be changed by different build
styles
This would remove the need for a lot copy/paste operations and
duplication in target settings
Regards
Ian Clark
DrawWell Technologies Ltd.
www.drawwell.com
_______________________________________________
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.