Re: XcodeMigration tool and Perforce
Re: XcodeMigration tool and Perforce
- Subject: Re: XcodeMigration tool and Perforce
- From: Chuck Hill <email@hidden>
- Date: Wed, 22 Oct 2008 19:36:44 -0700
Hi Denise,
On Oct 22, 2008, at 7:07 PM, email@hidden wrote:
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?
I strongly suggest that you do the opposite: reorganize the structure
of the project in Perforce to match the Eclipse project. The layout
is a convention supported by the standard Ant builds. You can change
it, but you are going to be working against the tools.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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