[p4] Eclipse plugin - keeps saying '{path} not under client'sroot'- stumped

steve@vance.com steve at vance.com
Fri Oct 26 17:42:31 PDT 2007


First, are you using the Cygwin build of p4? That handles some things a
little better.

Second, search the list. There is some information that people have posted
in the past regarding path translation and mounting options to make Cygwin
work smoothly.

Steve

Original Message:
-----------------
From: Dmitry Shulga dmitry.shulga at gmail.com
Date: 	Fri, 26 Oct 2007 14:41:02 -0700
To: rick.reumann at gmail.com, steve at vance.com, perforce-user at perforce.com
Subject: RE: [p4] Eclipse plugin - keeps saying '{path} not
under	client'sroot'- stumped


Hi guys!

I am having the same issue but with Cygwin. Whenever I try to do any
perforce related operation in opened Cygwin window, I am getting the
following:

	[14:36]$ p4 files *
	Path '/p4\code' is not under client's root 'C:/p4'.
	Path '/p4\p4tar.pl' is not under client's root 'C:/p4'.
	Path '/p4\p4untar.pl' is not under client's root 'C:/p4'.
	Path '/p4\tools' is not under client's root 'C:/p4'.

I don't have any mounts except for this one:

	[14:36]$ mount
	c: on / type system (binmode)

My client specs as follows:

	Root:	C:/p4
	Options:	noallwrite noclobber nocompress unlocked nomodtime
normdir

I tried both C:\p4 and the one above - useless. 

So what can I do to be able simply check out a file in Cygwin window? I am
getting annoyed with necessity to go back and forth between cmd windows.

-D


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Rick Reumann
Sent: Friday, October 26, 2007 6:55 AM
To: steve at vance.com
Cc: perforce-user at perforce.com
Subject: Re: [p4] Eclipse plugin - keeps saying '{path} not under
client'sroot'- stumped

On 10/26/07, steve at vance.com <steve at vance.com> wrote:

> I've generally just created a new workspace for virtual machines. You
> should definitely try that if you can.

Ah, that was what I was thinking the whole time I should get done, but
I thought it was something that an admin had to setup for me so I
figured I'd wait on pursuing it (my initial client workspace was
already setup on this machine, so my ignorance about perforce assumed
it was an admin function). Turns out I was able to just create another
one myself and all is well.

I will be interested to try to figure out what was up with the
perforce plugin though.

Thanks again for your help! Suggesting a new workspace was perfect.
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user


--------------------------------------------------------------------
myhosting.com - Premium Microsoft® Windows® and Linux web and application
hosting - http://link.myhosting.com/myhosting




More information about the perforce-user mailing list