Re: Old: Command-K not compiling
Re: Old: Command-K not compiling
- Subject: Re: Old: Command-K not compiling
- From: Andreas Grosam <email@hidden>
- Date: Mon, 4 Jul 2005 21:42:31 +0200
On 04.07.2005, at 20:23, Chris Espinosa wrote:
On Jul 4, 2005, at 11:09 AM, Andreas Grosam wrote:
I just ran into the "Command-K not compiling" problem (referring to
messages from 9. Jun 2005 with this subject).
It is pretty annoying. Is there a workaround without changing
everything to full paths?
If it has to do with ../ style path references, it's fixed in 2.0,
broken in 2.1, and should be fixed again soon. Unfortunately the only
workaround is to move your project file to the top level of your
project directory, then fix up all the file references.
I'm really glad to hear that this will be fixed soon! :-)
Well, my project is not at the top level. I have a folder "Source", and
it is set "Relative to Project", having this Path: "../..Source"
I also specified a search path in the target setting which is:
Header Search Paths = ${SRCROOT}/../..Source
It looks like this works, for the build system and the compiler.
The reason for this is, I have sub folders in folder Source, and my
files using this include idiom:
#include <sub/header.h>
btw, just an idea:
per default, the build variable SRCROOT points to the directory where
the XCode project is located. Can we change this? If yes, how and what
side effects does it have?
Shouldn't we have a constant variable named "PRJROOT", which always
points to the directory where the xcode project is located?
Anyhow, the idea is, if we could change the SRCROOT build setting
variable (for each target separately!), for instance in the "Target
Info" panel, specifying relative paths would become a bit more easier,
multi target projects would become more structured and the paths would
be more readable, for instance:
specifying a search path in a target might look like this:
Header Search Paths = ${SRCROOT}/include
Suppose we would have PRJROOT, and if we have a project with two
targets, and in each I set this in the Target Info panels:
Target1:
SRCROOT = ${PRJROOT}/../../Prj1
Header Search Paths = ${SRCROOT}/include
Target2:
SRCROOT = ${PRJROOT}/../../Prj2
Header Search Paths = ${SRCROOT}/include
Well, another problem here is, we still can't cross reference settings
from Target1 to Target2 (or is it?) If this would be possible, it could
look like this:
Target2:
SRCROOT = ${PRJROOT}/../../Prj2
Header Search Paths = ${SRCROOT}/include ${Target1.SRCROOT}/include
(Uhps, it becomes off topic ;-) )
Regards
Andreas
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
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