#import association Path
#import association Path
- Subject: #import association Path
- From: René van Amerongen <email@hidden>
- Date: Tue, 25 Jul 2006 16:02:47 +0200
Subject text forgotten
I'v been trying to track down a issue with XCode and #import files.
lets say I have
/../../debugUnit/myDebug.h
/../../debugUnit/myDefUnitSettings.h
/myProject/myHeader.h
/myProject/myClass.m
/myProject/myDefUnitSettings.h <-= is a copy from debugMacro/
myDefDebugSettings.h and placed in myProject
/../../debugUnit/myDebug.h <-= is just inserted
inside /../../debugUnit/myDebug.h I do have #import
"myDefUnitSettings.h"
inside /myProject/myHeader.h I do have #import "myDebug.h"
XCode accepts my changes which I made in /myProject/
myDefDebugSettings.h. But still use /../../debugUnit/
myDefDebugSettings.h
It drove me nuts why my changes in some macro's didn't work ( any
more ).
If this intended, wouldn't be nice if XCode has the order to search
first what's inside the project and then searches in association with
the original source file.
Or is there any setting who can settle this?
Any opinion about this?
_______________________________________________
_______________________________________________
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
| References: | |
| | >(no subject) (From: René van Amerongen <email@hidden>) |