Re: Project file turns into folder
Re: Project file turns into folder
- Subject: Re: Project file turns into folder
- From: "Edward K. Chew" <email@hidden>
- Date: Mon, 30 Oct 2006 10:44:32 -0500
On Oct 27, 2006, at 18:51, Laurence Harris wrote:
On Oct 27, 2006, at 3:45 PM, Edward K. Chew wrote:
On Oct 27, 2006, at 11:30, Steve Mills wrote:
Perhaps your Launch Services db needs a rebuild? Try this in
Terminal (all one line):
/System/Library/Frameworks/ApplicationServices.framework/Versions/
A/Frameworks/LaunchServices.framework/Versions/A/Support/
lsregister -f
/Developer/Applications/Xcode.app
I had this happen after I booted from a Leopard seed and went to
open a project. Took me a few seconds to realize that I had not
yet installed Xcode on that volume, so Finder didn't know that
a .xcodeproj was supposed to be a package.
Alas, this didn't seem to have any appreciable effect.
This is very odd. The Finder uses Launch Services to determine when
something is a package and which application should open it. If the
extension on the package is correct and your LS database is up to
date, it should all just work.
Well, there is one anomaly I noticed in the way things are set up on
this machine. The Developer directory had been moved over onto a
larger external partition and symlinked back to /Developer. I don't
even remember doing this. I suppose that might be causing some
problems. I tried lsregister again on the true path to Xcode.app,
but to no avail.
lsregister can take a while to do its work. Are you sure you let it
run to completion?
Hmm... I think I just quit Terminal and logged out once I got the
command prompt back. Are you saying lsregister daemonizes itself or
something? I never checked for that.
On Oct 27, 2006, at 11:36, Sean McBride wrote:
On 2006-10-27 11:30, Edward K. Chew said:
Nah, the extension is still just ".xcodeproj". Is there anything
else that makes a package a package? The one in question contains
four files:
project.pbxproj
ted.mode1
ted.mode2
ted.pbxuser
Is there some Finder flag I need to set, or am I being too old
school?
There is the 'bundle bit'. See 'man SetFile'. But Xcode.app
does not
set the bundle bit on projects it creates, which is why .xcodeproj's
appear as folders on machines that do not have Xcode.
Okay, I set the bundle bit and, after logged out and returning,
the project was looking like a single file again, albeit one with
a blank icon. I told it in Get Info to open up under Xcode, and
now everything seems to be fine,
Are you saying that it gets the right icon after Xcode opens it?
It looks like the first project I told to open in Xcode got its icon
back, but I chose the option to map all .xcodeproj packages onto
Xcode, and the others still have blank icons. They do, however,
launch into Xcode when double-clicked (provided I have forced them to
be treated as files by setting the bundle bit).
though it looks like I will have to go and set the bundle bit on
all my other projects. (Fortunately, there aren't too many yet,
since I'm gradually working my way over from CodeWarrior.)
I can't help but think I need to do the OS X equivalent of
rebuilding the desktop, whatever that might be.
It's that thing you did in Terminal that you said didn't have any
appreciable effect. ;-)
Ah.
Well, at least I have a workaround now. Fortunately, this is no
longer my primary machine. I keep it around for debugging PowerPC
code. (There's a lot of Altivec stuff in there.)
-Ted
_______________________________________________
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