Xcode fails to write source files that have hard links or if the folder has a symbolic link
Xcode fails to write source files that have hard links or if the folder has a symbolic link
- Subject: Xcode fails to write source files that have hard links or if the folder has a symbolic link
- From: Walter <email@hidden>
- Date: Sat, 09 Jun 2007 18:02:32 -0400
- Thread-topic: Xcode fails to write source files that have hard links or if the folder has a symbolic link
When I attempt to link a source file to another location using ln, Xcode
refuses to save to that file any longer. The error message isn't real
useful either:
The document <filename> could not be saved.
Does anyone know of a good reason why Xcode prevents saving these files?
Is there a workaround besides copying the files?
If the files are copied, subversion doesn't know about changes to copied
files and remembering which files changed becomes a nightmare...
I know lots of people are going to say "Why would you even want to do
that?". Well, I'm developing plug-ins for Adobe products that require a
different SDK and source folder structure for each version. I've #ifdef'd
the differences between versions, so each version builds from the exact same
source code. In the past I've used a script that calls ln to duplicate the
source files to each location that its needed in, after checking out from
subversion. This has worked very well in the past and I'd like to continue
developing in that way.
Walter
_______________________________________________
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