Re: SCM in Xcode 3.0
Re: SCM in Xcode 3.0
- Subject: Re: SCM in Xcode 3.0
- From: Dmitry Markman <email@hidden>
- Date: Thu, 21 Feb 2008 00:59:27 -0500
if your project and sources are not so far in file hierarchy
it would be sufficient just change project root
no need for any reorganization
for example
if your project exists in the folder f0/f1/f2/p
and your sources exists in the folder f0/f1/s
just make you root project as ../../
and it should work, at least it worked for me
On Feb 20, 2008, at 9:13 PM, Dr. Rolf Jansen wrote:
Many thanks for the answer. Next weekend, I will either re-organize
my projects or even switch back to Xcode 2.5. Working a while with
Xcode 3.0 at my PowerBook G4 1.5 GHz, I found out that editing and
moving around in the source code is significantly slower than it was
with 2.5. Too frequently, Xcode 3.0 simply hangs for a second or so,
when scrolling the source files.
Best regards
Rolf
Am 20.02.2008 um 16:29 schrieb Rob Lockstone:
I think you're going to have to bite the bullet, join the rest of
us, and do the reorganization. Representatives from Apple have
stated a couple times on this list that they are aware of this
issue and are looking at how they might "fix" it in a future
release of Xcode. Of course, that is NO guarantee that the behavior
will be changed.
Unfortunately, if the behavior is ever changed, all of us who have
made the switch from 2.4/5 to 3.0 will have already done the hard
work of reorganizing our projects to conform with this particular
requirement.
C'est la vie.
Trust me, I know exactly how you feel as I spent several hours just
this past weekend reorganizing my projects so I could make the
switch to 3.0.
Rob
On Feb 20, 2008, at 03: 23, Dr. Rolf Jansen wrote:
I am a long time PB/Xcode user, and I am using Xcode for several
different coding purposes. Among these are web applications
(collaborative effort), open source projects (read-only), and my
own Pascal, FORTRAN, C/Obj-C projects. The following happened to
work for me since Xcode was Project Builder.
For several of my projects, the Xcode project directory is
different from the source directory, and the SCM management files
(CVS or SVN) reside together with the sources in their respective
sub-directories. Xcode up to 2.5 automatically identified the
correct SCM management directories and operated seamlessly on it.
This worked for me even for SCM source trees hosted at different
locations which are collected in the same Xcode project. I
searched in the archives before writing to here, and I found
somebody stating in April last year that this should not work. <http://lists.apple.com/archives/xcode-users/2007/Apr/msg00237.html
> This is not true for Xcode up to 2.5, but unfortunately, it
seems to be true for Xcode 3.0.
To no avail, I tried for some hours now to find a way to tell
Xcode 3.0 not to use the entries of the newly introduced
repository set up, but of the more generic SCM management
directories, that are outside of the project directory. I found
out, that I can leave the repository set up almost empty and Xcode
would take the generic SCM settings, but the show stopper seems to
be, that Xcode refuses to activate SCM if it does not find SCM
management files in its project directory.
Please, do not take this as a rant, and of course, I can resolve
this by re-organizing my projects. Anyway, before I sit down for
several hours for doing this, I wanted to ask here, whether there
is a simple switch for making Xcode 3.0 behave as before.
Many thanks in advance for any help.
Best regards
Rolf Jansen
_______________________________________________
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
Dmitry Markman
_______________________________________________
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