copyplist and read-only files
copyplist and read-only files
- Subject: copyplist and read-only files
- From: Jens Miltner <email@hidden>
- Date: Thu, 02 Oct 2008 15:25:29 +0200
Hi,
after upgrading our production build system to Xcode 3.1.1, we had
problems with builds failing because copyplist failed copying files.
It turned out that this was because we check out files (as an
additional security measure to avoid accidental modifications) read-
only on our production system. When copyplist tries to copy such a
read-only file for the second time into the product package, it fails
with an permission error.
This didn't happen before and I suspect it it because those files were
not identified as plists before (or at least they were not copied
using a special tool, but rather by the default PbxCopy tool (or
whatever it's called) that just copies files into the product package.
After switching to Xcode 3.1.x, editing the plist files marked them as
plists in the xcode projects, thus the copy files phase will use
copyplist instead of the 'dump' copy tool, which fails to overwrite
read-only files in the product bundle (filed as RADAR #6263824).
I found that I can fix the tool myself by adding an 'rm' command just
before the 'cp' command the ruby script issues (or by adding a '-f'
option to the cp command), but of course, I'd probably have to re-
apply this change for each Xcode update...
Is there any reason behind this behavior, or is just a plain bug?
Is there any build settings I should modify to force overwrite read-
only files in copy files build phases in Xcode 3.1.x?
Thanks,
</jum>
_______________________________________________
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