• 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: import PB project
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: import PB project


  • Subject: Re: import PB project
  • From: Sherm Pendley <email@hidden>
  • Date: Thu, 17 Apr 2003 02:09:07 -0400

On Thursday, April 17, 2003, at 01:37 AM, John Q. wrote:

OK it is both the December2002 version of the developer tools!!

You shouldn't need to import the project, then - just opening the .pbprj file as usual should work just fine.

But One from the list has written that the project builder have had problems
with pathes!! He said:

One thing project builder is bad at is absolute paths. Example, say on your old computer you had "/Users/user1/main.m" and on your new computer it's "/Users/user2/main.m" project builder may not find the file. Go through each file in your project, if the file is "red" then you'll have to add it again to your project. When you add files make sure you select "relative paths".

Actually, that was me. ;-)

If no files are red, it could also be a permissions problem. Did you use 'tar' to package up the project folder and move it to your new machine? If so, and the login that you used to create the tarball doesn't exist on the new machine, permissions could be fubar.

To check for this, do an 'ls -l' in a Terminal window, to get a long-format listing of the folder contents. The columns in the list are the file's mode, the number of links to it, the owning user, the owning group, the size in bytes, the last modified date, and the file name. If the owning user or group is listed as a number instead of being listed by name, or if the user name listed is not the one you're using on your new machine, you have a permissions problem.

You can fix permissions with the 'chown' tool. Assuming you want the files to be owned by a user named 'JohnQ', and the 'staff' group, the command would look like this:

sudo chown -R JohnQ:staff *

I apologize if this is too basic. For all I know, you may be a 20-year UNIX veteran who's new to the Mac. If you are, no offense is meant - I don't know you, and you could just as easily be a 20-year Mac veteran who's new to the whole command-line thing.

sherm--
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: import PB project
      • From: "John Q." <email@hidden>
References: 
 >Re: import PB project (From: "John Q." <email@hidden>)

  • Prev by Date: Re: import PB project
  • Next by Date: Re: How to know if Classic is running?
  • Previous by thread: Re: import PB project
  • Next by thread: Re: import PB project
  • Index(es):
    • Date
    • Thread