Re: Xcode relative path for Makefile builds
Re: Xcode relative path for Makefile builds
- Subject: Re: Xcode relative path for Makefile builds
- From: Fritz Anderson <email@hidden>
- Date: Fri, 23 Oct 2009 14:58:19 -0500
On 21 Oct 2009, at 2:41 PM, Pelaia II, Tom wrote:
I am working on a project that uses Make files. I am editing the
source code in Xcode, and would like to build using Xcode. Building
works fine, but the error messages won't open in the source code
because the relative paths in the Makefile aren't relative to the
location of the Xcode project or even relative to the Makefile since
the Makefile has a complex dependency. I really can't modify the
Makefile to accommodate Xcode because it is a shared project and to be
honest the Makefile nesting rules are quite complex. Placing the Xcode
project file in a location to satisfy the relative path would place it
in an awkward location. I want my project file at the top.
Is there a way to tell Xcode how to interpret the relative paths of
files that appear in the build errors?
I asked much the same question about a week and a half ago, and got
nothing back. I assume the functionality simply isn't there.
I seem to remember (I'm willing to be corrected) that Xcode 3.0 would
try to do what we want — I'd guess that it took the filename, assumed
it would be unique in the project tree, and opened an editor on the
first file with that name. Better than nothing, though I suppose
actually harmful if the tree contains more than one file of the same
name.
External-build projects in Xcode get symbol indexing (with the
attendant improvements in searching and syntax highlighting), and a
graphical editor. I'm hard-pressed to think of other advantages over
Emacs for makefile projects.
— F
_______________________________________________
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