c++ target fails, upgrading project 3.1 to 3.2
c++ target fails, upgrading project 3.1 to 3.2
- Subject: c++ target fails, upgrading project 3.1 to 3.2
- From: Daniel Stein <email@hidden>
- Date: Tue, 07 Aug 2012 19:45:01 -0700
I have a cocoa project with a c++ back-end executing in an NSTask.
Upon migrating the project from my 10.5 installation using xcode 3.1
to 10.6 using xcode 3.2, the c++ tool target fails to compile. The c++
code links with some static libraries.
I have no trouble with this code if I make a new project in 3.2 to
build a command line tool. I add the source, the libraries, and make a
path to the relevant headers, but all hell breaks loose when simply
try to port the whole project from 10.5. I've copied in the static
libraries and made a path to the <include> but nothing seems to work
right any more.
I suppose my best bet is to rebuild the entire project starting as a
shell tool in 10.6, and then add the Cocoa classes and nib files to a
second target, and set things up from there.
I just thought I would ask if there is a simple compilation flag I can
change in the build settings for my back end target in the old
project, so that the compiler will deal with the c++ code.
It wouldn't be so bad to add the cocoa target later, but the feeling
that there would be a simple flag I could set to get xcode 3.2 to deal
with it. It is a working project in 3.1 under 10.5, and I am just
making my way toward having software for which I can build universal
binaries.
I have updated several projects, pure cocoa or with standard C back
offices, and this is the first real hangup I have encountered. Any
help much appreciated.
Most of my xcode experience is in 2.5 under Tiger on ppc machines. I
know, I know. I feel and look like a dinosaur.
_______________________________________________
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