• 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
XcodeMigration tool and Perforce
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

XcodeMigration tool and Perforce


  • Subject: XcodeMigration tool and Perforce
  • From: email@hidden
  • Date: Thu, 23 Oct 2008 02:07:37 +0000

I'm in the process of migrating our frameworks and apps from Xcode to Eclipse and WOLips.  We use Perforce for SCM, so my Perforce workspace is at a particular location on my machine (/Users/dhoward/DevP4) and Xcode is fine with that.  I need my Eclipse workspace for a given project to continue talking to Perforce.  I already discovered that the /tmp/migrations directory where the XcodeMigration tool constructs its Eclipse versions of Xcode projects is not a good final destination.  How can I do this?  Must I reorganize the file structure of the project as it is in Perforce now?

Denise
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: XcodeMigration tool and Perforce
      • From: Chuck Hill <email@hidden>
  • Prev by Date: Re: [Wonder-disc] SOLVED: Zombie sessions
  • Next by Date: Re: XcodeMigration tool and Perforce
  • Previous by thread: Re: Minifying Javascript during build
  • Next by thread: Re: XcodeMigration tool and Perforce
  • Index(es):
    • Date
    • Thread