Re: Porting projects from Windows
Re: Porting projects from Windows
- Subject: Re: Porting projects from Windows
- From: Thomas Hauk <email@hidden>
- Date: Mon, 15 Sep 2008 13:49:40 -0700
On Sep 12, 2008, at 4:14 PM, Jonathan Prescott wrote:
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.
Thanks for your response. I updated to 3.1.1 to be sure, and your
steps did indeed work. This effectively eliminates one of the things
that bugged me the most with Xcode.
However, there still remains one big thing: I can't see the source
files of my dependencies. For example, when I open up A1.xcodeproj,
I'd like to see the source files for P1.xcodeproj. Is there a way I
can do this?
If not, Apple, please can you add this in?
Without the ability to see files of dependencies, I'm not sure my
client will want me continuing to use the 1-project-per-package
pattern, since it requires one of two annoying procedures to find
files when my top-level application project is open; either (1)
manually navigating to source files in the Open dialog, each time I
want to look at one, or (2) having to keep each package's project
window open (which could amount to at least a dozen with one of our
applications).
I've also hoped to hear more about the "monolithic" approach, but so
far there haven't been any responses -- i.e. put all source files for
all packages into a single .xcodeproj.
T
--
"Some people, when confronted with a problem, think 'I know, I'll use
regular expressions.' Now they have two problems."
-- Jamie Zawinski, in comp.lang.emacs
_______________________________________________
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