Re: Xcode 3.1 builds fails for OS X Cocoa apps (copystrings)
Re: Xcode 3.1 builds fails for OS X Cocoa apps (copystrings)
- Subject: Re: Xcode 3.1 builds fails for OS X Cocoa apps (copystrings)
- From: Michael Rawdon <email@hidden>
- Date: Mon, 14 Jul 2008 14:14:39 -0700
Hi Jim -On Jul 13, 2008, at 2:41 PM, Jim Fridlund wrote: Hi all. I just joined the list in hope that someone can help me with my Xcode problem. I am using a MacBook Pro with Xcode 3.1 installed (I tried iphone_sdk_final.dmg and xcode31_2199_developerdvd.dmg). Previously, I had Xcode 3.1 beta versions for iPhone development. I am able to build for iPhone apps just fine, but I would also like to build Cocoa apps for OS X using Xcode.
As a simple example, I create a new project as a Cocoa application. When I click on 'Build and Go', I get the following errors from the build output:
CopyStringsFile /Users/jim/Test/build/Debug/Test.app/Contents/Resources/English English.lproj/InfoPlist.strings: Insecure operation ...
CopyStringsFile /Users/jim/Test/build/Debug/Test.app/Contents/Resources/English.lproj/InfoPlist.strings English.lproj/InfoPlist.strings mkdir /Users/jim/Test/build/Debug/Test.app/Contents/Resources/English.lproj cd /Users/jim/Test /Developer/Library/Xcode/Plugins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings --validate --inputencoding UTF-16 --outputencoding UTF-16 English.lproj/InfoPlist.strings --outdir /Users/jim/Test/build/Debug/Test.app/Contents/Resources/English.lproj English.lproj/InfoPlist.strings: Insecure operation
It doesn't seem to like the copystrings command. If I manually invoke the copystrings command from the shell, I do not get the errors and it exits with status 0.
[...] First, building from the command line appears to work. Second, the command line build doesn't use copystrings. I'm relatively new to Xcode so I don't know why the behavior would be different. In any case, I thought having installed Xcode 3.1 beta for iPhone development was the reason why I was unable to build applications for OS X, but I now have the final version Xcode 3.1 installed and I still see the problem. I'm thinking there must be something missing in my environment? Any help greatly appreciated. Thanks in advance.
copystrings is a script which invokes a tool named iconv, but it does so by looking for it via the user's PATH environment variable. We've gotten at least one report of it finding a different iconv in a different directory than the default one in /usr/bin, and that other copy doesn't work as Xcode expects. It's entirely possible that the PATH in your GUI environment is different from the one in your shell, and that's what's happening.
In that case, you have two alternatives:
1) You could hack your copy of copystrings to explicitly invoke /usr/bin/iconv, or 2) You could see if there's an extra copy of iconv lying around and remove it.
(This issue will be fixed in a future release of Xcode.)
Of course, this might not actually explain your issue, but it's my best guess!
--
Michael Rawdon email@hidden
Xcode Developer Apple Inc., Cupertino CA
|
_______________________________________________
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