• 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: Cannot compile, Volume name changed
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cannot compile, Volume name changed


  • Subject: Re: Cannot compile, Volume name changed
  • From: Sherm Pendley <email@hidden>
  • Date: Fri, 13 Oct 2006 10:28:16 -0400

On Oct 13, 2006, at 10:11 AM, Lorenzo wrote:

I have my XCode project on a DMG volume.
I mount the volume and instead of the original mount point
    /Volumes/MyApps
today I get the mount point
    /Volumes/MyApps 1
Now there is no reason why MacOS X has to change the mount point
appending " 1" to the volume name, because this is the only one volume
labeled "MyApps" mounted on the desktop.

There's also no reason why it shouldn't be allowed to do that. Depending on a specific mount point is fragile and shouldn't be done.


Of course my project won't compile because the built pathname has changed,
and, even if I change the projects paths to the new "MyApp 1" it doesn't
work because Unix doesn't accept spaces in a pathname

Unix handles spaces perfectly well.

Most shells use spaces as a delimiter between arguments; to prevent that from happening in those shells, you need to precede them with an "escape" character - usually a backslash - to let the shell know that the following space is to be taken literally instead of as a delimiter. Alternatively, you can use quotes to delimit arguments that contain spaces.

The problem is that Xcode (and Project Builder before it...) has had long-standing difficulties getting the quoting correct in the shell commands is issues. It's not a Unix limitation; it's an Xcode bug.

How to solve this problem?

First, if you're not using the latest Xcode for your OS version, you should seriously consider upgrading.


As a workaround, "get info" on your project files, and under "path type" select "relative to project" instead of "absolute path". That will allow you to move your project directory anywhere you like without it losing track of your files.

sherm--

Web Hosting by West Virginians, for West Virginians: http://wv-www.net
Cocoa programming in Perl: http://camelbones.sourceforge.net


_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Cannot compile, Volume name changed
      • From: Lorenzo <email@hidden>
    • Re: Cannot compile, Volume name changed
      • From: Lorenzo <email@hidden>
References: 
 >Cannot compile, Volume name changed (From: Lorenzo <email@hidden>)

  • Prev by Date: Cannot compile, Volume name changed
  • Next by Date: Sending an ASCII string to a specific IP address
  • Previous by thread: Cannot compile, Volume name changed
  • Next by thread: Re: Cannot compile, Volume name changed
  • Index(es):
    • Date
    • Thread