Re: relative path not "sticking"
Re: relative path not "sticking"
- Subject: Re: relative path not "sticking"
- From: Adhamh Findlay <email@hidden>
- Date: Tue, 12 Feb 2008 21:46:21 -0600
I just ran "find . -name "*Xcode*" in my home directory. I deleted
everything it found, plus that adhamh.* files in the xcodeproj
directory and the problem still exists...
adhamh@imac:~:>rm -r .Xcode
adhamh@imac:~:>rm -r "./Library/Application Support/Developer/Shared/
Xcode"
adhamh@imac:~:>rm -r "./Library/Application Support/Xcode"
adhamh@imac:~:>rm -r ./Library/Caches/com.apple.Xcode
adhamh@imac:~:>rm -r ./Library/Preferences/com.apple.Xcode.plist
On Feb 12, 2008, at 5:52 PM, Adhamh Findlay wrote:
Well, I don't think its a bug because the guys I'm working with
don't have this problem.
Here's our structure:
projectDir
Source
English.proj
where Source is for source files and English.proj is for xibs.
To reproduce the problem I do the following:
1. Check out the project from subversion
2. Open the checkout project file
3. Add a new Objective-C file to the project's Source directory
6. Get info on the new file and see that its path is "Absolute Path"
I've tired removing the adhamh.mode1v3, adhamh.pbxuser and just
about every other Xcode plist I could find nothing made a different.
When I create a new test project that is not using subversion but
that has the same directory structure I can not reproduce this
problem.
Also, if I can't reproduce on a new user account.
1. Create a brand new user account
2. launch terminal and checkout the source.
3. Open the checkout project file
4. Select the all the defaults in the Xcode setup assistant
5. Add a new Objective-C file to the project's Source directory
6. Get info on the new file and see that its path is "Relative to
Enclosing Group".
So it seems pretty clear that its something specific to this user
account and this project as I can't reproduce the issue outside of
this project and user account. Plus my co-workers can't reproduce it.
Thanks,
Adhamh
On Feb 12, 2008, at 5:30 PM, Scott Tooker wrote:
What sort of project structure do you have? I know that in the past
we spent some effort on ensuring that by default any new files
added to a project would be project relative unless they were
pointing to root locations (for example, /usr/include/blah.h).
Can you provide a more specific example of what you are seeing? I'd
file a bug if you are seeing files that are underneath your project
root get set to be absolute. Even files that are "up and over" from
the project root should be set as project relative.
Scott
On Feb 12, 2008, at 2:58 PM, Adhamh Findlay wrote:
Hi All,
Is there a way to get "relative path" to always be selected when I
add new files? Even after I use "relative path" the next time I
add a file "default" is selected and default is absolute path...
This is on Xcode 3.
Thanks,
Adhamh
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@apple.com
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
_______________________________________________
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