Re: Porting projects from Windows
Re: Porting projects from Windows
- Subject: Re: Porting projects from Windows
- From: Jonathan Prescott <email@hidden>
- Date: Fri, 12 Sep 2008 19:14:35 -0400
Did you make sure that the P1 target (the library) was a direct
dependency for A1 (the application)? Open up the A1 project. I'm
assuming in the Groups&Files list, the P1 project is there. Double-
click on the A1 target, and pick the "General" pane. If the P1 target
(not libP1.a, but the P1 target from the P1.xcodeproj) is not being
seen in the Direct Dependencies box, hit the "+" sign at the bottom of
the box. You should get a drop-down list with the P1 target shown
coming from the P1.xcodeproj. Select that and close out the A1 target
editor. Now, rebuild A1 and it should rebuild P1 before it rebuilds
A1. Just tried it out on Xcode 3.1, and it worked like a charm. I
use it for a lot of my stuff where I have standard frameworks I build
each its own project, and separate application and tool projects. If
I happen to make changes to the standard frameworks, I just rebuild
the application and the frameworks get re-built prior to the
application or tool.
It's all discussed in the Xcode Project Management Guide, which is in
the Developer Tools docset.
Jonathan
On Sep 12, 2008, at 6:16 PM, Thomas Hauk wrote:
On Sep 10, 2008, at 4:44 PM, David Dunham wrote:
Please copy the list.
Apologies as I made a mistake of only clicking "Reply". I have noted
it this reply, which is going to both you and the list.
Say I have Applications A1 and A2. A1 uses packages P1 and P2, and
A2 uses packages P1 and P3.
With Visual Studio, I can create a solution for A1 that includes
A1, P1 and P3. While working with this solution open, if I make a
change to a source file that lives in P3, Visual Studio
automatically knows the entire solution needs a rebuild. I can
also create a solution for A2 and I can use the same project file
for P1.
In Xcode, how do I accomplish all of this? Most importantly, the
ability for the IDE to automatically know when a dependency needs
to be recompiled. If at all possible, it would also be nice to
keep just a single window open for all of this, and not one per
package, and also have to manually determine when a package needs
to be recompiled.
Drag P1.xcodeproj into A1.xcodeproj.
In the Target Info for A1, be sure P1 is a direct dependency.
I think you may also need to make sure there's a check on libP1.a
(in the View > Detail window).
This did not work.
I created a brand-new C library project and C application project,
P1 and A1, and followed your steps. P1 contains p1.c and p1.h. I
modified p1.c from within A1.xcodeproj and hit "Build". P1 did not
get automatically re-compiled.
Xcode really is not really designed for convenient application
development where you have a collection of packages (some may be
external, some may be internal) and want to have a top-level project
that uses these projects. I believe I am forced to use a
"monolithic" approach. As such, I will re-state one of the questions
I asked in my original e-mail, and hopefully someone can answer it:
"One method to resolve this that I've found using Google is to have
all the code for all the packages lumped into a single Xcode
project. At present, we have more than one application in this
project, all of them using different sets of packages. Would this
"monolithic" approach require me to have one Xcode project per
application (resulting in a huge mess of having to manually track
setting changes)? Or can I set up a single Xcode project to compile
three very different applications using different sets of shared
package sources?"
T
--
"Computer games don't affect kids. I mean, if Pac-Man affected us as
kids, we'd all be running around in darkened rooms, munching pills
and listening to repetitive music."
-- Marcus Brigstocke
_______________________________________________
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
_______________________________________________
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