• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Problem compiling first Cocoa app in Xcode 3.1
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem compiling first Cocoa app in Xcode 3.1


  • Subject: Re: Problem compiling first Cocoa app in Xcode 3.1
  • From: "Paul Denlinger" <email@hidden>
  • Date: Sun, 20 Jul 2008 17:43:31 -0700

I used the "open .bash_profile" command to see the path and it is:

export PATH="/opt/local/bin:/opt/local/sbin:$PATH" 

Following Sam Net's instructions, I have edited the path variables to:

export PATH="/opt/local/bin:/opt/local/sbin:/usr/bin:sw/bin$PATH"

Just tried running the xcodetestrun app again and got the same error message:

Building target "xcodetestrun" of project "xcodetestrun" with configuration "Release" — (1 error)

    cd /Users/pdenlinger/Sites/xcodetestrun

    /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings --validate --inputencoding UTF-16 --outputencoding UTF-16 English.lproj/InfoPlist.strings --outdir /Users/pdenlinger/Sites/xcodetestrun/build/Release/xcodetestrun.app/Contents/Resources/English.lproj

error: can't exec '/Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings' (No such file or directory)

error: can't exec '/Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings' (No such file or directory)

error: can't exec '/Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings' (No such file or directory)

Build failed (1 error)


Paul D


On Sun, Jul 20, 2008 at 5:31 PM, Conrad Taylor <email@hidden> wrote:
Hi, you only need .bash_profile or .profile but not both because only one will be read.

Good luck,

-Conrad


On Sun, Jul 20, 2008 at 5:24 PM, Paul Denlinger <email@hidden> wrote:
I have a question re .bash_profile  and .profile. 

The instructions in the directions for the installation for .bash_profile at http://www.buildingwebapps.com/articles/17-setting-up-rails-on-leopard-mac state the following for setting up the environmental variables for the .bash_profile file say:

"After MacPorts completes installation, you need to adjust your command line PATH environment variable so you can run theport command.

Fire up the Terminal program and enter the command:

    $ open .bash_profile

Note that there is a period in front of "bash_profile". The bash shell configuration file should open in the TextEdit program. If you don't have a .bash_profile, you can create a new one in your text editor and save it in your home directory.

(By the way, we recommend iTerm as a nice open source replacement for the Apple Terminal program.)

Inside of .bash_profile, find the line that starts with export PATH=, if present. You are going to insert the new directories used by MacPorts into your path:

    export PATH="/opt/local/bin:/opt/local/sbin:$PATH"

If you don't have a line that exports your PATH, use the text exactly as above. If you do already have such a line, add the/opt/local/bin:/opt/local/sbin: (note colons) after the first quote, but before any other paths. Here is an example:

    export PATH="/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/local/sbin:$PATH"

Save the file and close TextEdit. Open a new terminal window and have MacPorts update itself with the command:

    $ sudo port selfupdate

Now if I create a new .profile file with its own environmental variables, won't that create a path conflict? Don't the .bash_profile and .profile do one and the same function? So if I edit a file and set its environmental variables, shouldn't it just be one file and not two whose instructions which would potentially conflict with each other?

TIA

Paul Denlinger

On Sun, Jul 20, 2008 at 4:26 PM, Conrad Taylor <email@hidden> wrote:
Hi, I'm currently using a MacPorts Ruby installation and I'm not having any issues with XCode.  Thus, it appears to be something wrong with your installation.  At this time, my .profile looks like the following:

export PATH=/opt/local/bin:/opt/local/sbin:/opt/local/apache2/bin:${PATH}

Good luck,

-Conrad

On Sun, Jul 20, 2008 at 4:06 PM, Sam Net <email@hidden> wrote:
Hi Paul,

I had a similar problem when I was building WebKit from the cmd-line and I suspect that solution to my problem could also be the solution to your problem.

You will have to do one of the following:

1) Remove /sw/bin from your PATH environment variable (if it's there) - (i.e.  You will need to edit .profile),
2) Move /sw/bin to the end of PATH after /usr/bin so that system binaries take preference,
3) Upgrade the version of iconv that you have installed via MacPort,
4) Or edit the copystrings script to hard-code /usr/bin/iconv.

Essentially, you just need to ensure that /usr/bin is the first entry for PATH in your .profile file that is located in your home directory.  This will ensure that the System binaries take precedence over any other binaries that may have been inadvertently installed by MacPorts, Fink, etc.

You can use TextWangler (http://www.versiontracker.com/dyn/moreinfo/macosx/18529) or TextEdit (Apple application) to edit the .profile file in your home directory.  If the .profile file isn't in your home directory then you will need to create it.  If you are not to familiar with the shell and how to edit the .profile file then I would suggest having a look at: http://www.tech-recipes.com/rx/2621/os_x_change_path_environment_variable  . Here you will find a good tutorial that will help you to understand what you need to do.

Good luck!

- Sam





On 20 Jul 2008, at 23:29, Dmitri Goutnik wrote:

On Jul 21, 2008, at 2:00 AM, Paul Denlinger wrote:

Question: I know that there are quite a few people running Macports for their installs. Shouldn't they be running into the same error if Macports changes the default directories?


Paul,

I have ruby and RoR installed from Macports and it doesn't affect Xcode in any way - there's definitely something wrong with your installation.

The copystrings is a Ruby script that requires Ruby interpreter to be in a specific place - /usr/bin (as its first line says: #!/usr/bin/ruby - this is shell way of saying that the file is in fact a script and it should be executed with specified interpreter). "No such file or directory" errors that you are getting indicate that /usr/bin/ruby does not exist or does not have correct permissions.

As Greg noted, please post the output of :

(1) head -n 2 /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings

(2) ls -l /usr/bin/ru*

- Dmitri

_______________________________________________
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



--
Paul Denlinger
"Risk is about seeing opportunities when others see challenges."
Skype: pdenlingercbs
Profile:http://www.linkedin.com/in/pauldenlinger
Visit my blog at www.chinavortex.com
China | Business | Economy | Internet|Technology


DISCLAIMER:
The content of this email and any attachment may contain proprietary and confidential information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then deleting it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is not authorized and may be unlawful.

 _______________________________________________
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



--
Paul Denlinger
"Risk is about seeing opportunities when others see challenges."
Skype: pdenlingercbs
Profile:http://www.linkedin.com/in/pauldenlinger
Visit my blog at www.chinavortex.com
China | Business | Economy | Internet|Technology


DISCLAIMER:
The content of this email and any attachment may contain proprietary and confidential information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then deleting it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is not authorized and may be unlawful.
 _______________________________________________
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

References: 
 >Problem compiling first Cocoa app in Xcode 3.1 (From: "Paul Denlinger" <email@hidden>)
 >Re: Problem compiling first Cocoa app in Xcode 3.1 (From: Thomas Wetmore <email@hidden>)
 >Re: Problem compiling first Cocoa app in Xcode 3.1 (From: "Paul Denlinger" <email@hidden>)
 >Re: Problem compiling first Cocoa app in Xcode 3.1 (From: Thomas Wetmore <email@hidden>)
 >Re: Problem compiling first Cocoa app in Xcode 3.1 (From: "Paul Denlinger" <email@hidden>)
 >Re: Problem compiling first Cocoa app in Xcode 3.1 (From: Dmitri Goutnik <email@hidden>)
 >Re: Problem compiling first Cocoa app in Xcode 3.1 (From: Sam Net <email@hidden>)
 >Re: Problem compiling first Cocoa app in Xcode 3.1 (From: "Conrad Taylor" <email@hidden>)
 >Re: Problem compiling first Cocoa app in Xcode 3.1 (From: "Paul Denlinger" <email@hidden>)
 >Re: Problem compiling first Cocoa app in Xcode 3.1 (From: "Conrad Taylor" <email@hidden>)

  • Prev by Date: Re: Problem compiling first Cocoa app in Xcode 3.1
  • Next by Date: Re: Problem compiling first Cocoa app in Xcode 3.1
  • Previous by thread: Re: Problem compiling first Cocoa app in Xcode 3.1
  • Next by thread: Re: Problem compiling first Cocoa app in Xcode 3.1
  • Index(es):
    • Date
    • Thread