headers
Atul Prasad | 3 Jun 2008 13:11
Picon

[p4] Syncing all files to one folder

Hi,

Say I have multiple code units and all of them have a src and inc folder

I want all the files in all the inc folders to ONE folder include on my
client
How to write a client spec for that?

say a code unit A has inc and src
B has inc and src
C has inc and src

I want all inc files from A, B, C to go to one single folder INCLUDE

Thanks in advance..

--

-- 
Atul,
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 25 comments |
headers
Stephen Vance | 3 Jun 2008 13:32

Re: [p4] Syncing all files to one folder

//depot/A/inc/... //myworkspace/include/...
+//depot/B/inc/... //myworkspace/include/...
+//depot/C/inc/... //myworkspace/include/...

You just have to be careful when adding new header files. They will all 
go to the same place.

Steve

Atul Prasad wrote:
> Hi,
>
> Say I have multiple code units and all of them have a src and inc folder
>
> I want all the files in all the inc folders to ONE folder include on my
> client
> How to write a client spec for that?
>
> say a code unit A has inc and src
> B has inc and src
> C has inc and src
>
> I want all inc files from A, B, C to go to one single folder INCLUDE
>
> Thanks in advance..
>
>   

--

-- 
Stephen Vance
(Continue reading)

Permalink | Reply | 24 comments |
headers
Atul Prasad | 3 Jun 2008 14:09
Picon

Re: [p4] Syncing all files to one folder

Hi Steve,

Thanks for the response.

What you said is correct. However I have over 100 such code units(A, B, C..)
and it seems that there is some limit on the number of characters i can add
to the clientspec view. Is there some alternative that you can suggest..
Using wildcards or something??

On Tue, Jun 3, 2008 at 5:02 PM, Stephen Vance <steve <at> vance.com> wrote:

> //depot/A/inc/... //myworkspace/include/...
> +//depot/B/inc/... //myworkspace/include/...
> +//depot/C/inc/... //myworkspace/include/...
>
> You just have to be careful when adding new header files. They will all go
> to the same place.
>
> Steve
>
>
> Atul Prasad wrote:
>
>> Hi,
>>
>> Say I have multiple code units and all of them have a src and inc folder
>>
>> I want all the files in all the inc folders to ONE folder include on my
>> client
>> How to write a client spec for that?
(Continue reading)

Permalink | Reply | 20 comments |
headers
Tony Whitley (Hotmail | 3 Jun 2008 15:09
Picon
Favicon

Re: [p4] Syncing all files to one folder

I don't think there is a limit on the client spec size, we have some VERY 
large ones.

Can you use:

//depot/.../inc/... //myworkspace/include/...

I have tried something like that and it worked.

Though you'll have to be even more careful when adding new header files!

----- Original Message ----- 
From: "Atul Prasad" <atul.prasad <at> gmail.com>
To: "Stephen Vance" <steve <at> vance.com>
Cc: <perforce-user <at> perforce.com>
Sent: Tuesday, June 03, 2008 1:09 PM
Subject: Re: [p4] Syncing all files to one folder

> Hi Steve,
>
> Thanks for the response.
>
> What you said is correct. However I have over 100 such code units(A, B, 
> C..)
> and it seems that there is some limit on the number of characters i can 
> add
> to the clientspec view. Is there some alternative that you can suggest..
> Using wildcards or something??
>
> On Tue, Jun 3, 2008 at 5:02 PM, Stephen Vance <steve <at> vance.com> wrote:
(Continue reading)

Permalink | Reply | 18 comments |
headers
Robert Cowham | 3 Jun 2008 15:16
Picon

Re: [p4] Syncing all files to one folder

There is no underlying limit to characters in the view - I have created
client specs with tens of thousands of lines (not recommended mind you -
just for test!). 

You can't have a wildcard on the left hand side without also having it on
the right.

> -----Original Message-----
> From: perforce-user-bounces <at> perforce.com 
> [mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Atul Prasad
> Sent: 03 June 2008 13:09
> To: Stephen Vance
> Cc: perforce-user <at> perforce.com
> Subject: Re: [p4] Syncing all files to one folder
> 
> Hi Steve,
> 
> Thanks for the response.
> 
> What you said is correct. However I have over 100 such code 
> units(A, B, C..) and it seems that there is some limit on the 
> number of characters i can add to the clientspec view. Is 
> there some alternative that you can suggest..
> Using wildcards or something??
> 
> On Tue, Jun 3, 2008 at 5:02 PM, Stephen Vance <steve <at> vance.com> wrote:
> 
> > //depot/A/inc/... //myworkspace/include/...
> > +//depot/B/inc/... //myworkspace/include/...
> > +//depot/C/inc/... //myworkspace/include/...
(Continue reading)

Permalink | Reply | 0 comments |
headers
Greg Whitfield | 3 Jun 2008 15:39

Re: [p4] Syncing all files to one folder

As earlier replies have mentioned, you need to be careful with the
wildcards. You also need to ensure that there are no duplicate filenames
in the 100+ separate INC folders as this would not easily show up in the
one big folder.

Is there a deeper-seated problem here in the organisation of your code
and modules that you are trying to work around? 

I was just wondering why you need to do this. If it is a deployment
issue (e.g. you are an SDK writer and want to pool all of the public
includes together for users), then consider using a branch spec instead
and explicitly mapping these folders (with or without wildcards). It may
provide a more robustly trackable path, especially if edits are made on
files in the unified include folder.

Greg
~~~~

-----Original Message-----
From: perforce-user-bounces <at> perforce.com
[mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Tony Whitley
(Hotmail)
Sent: 03 June 2008 14:10
To: Atul Prasad; Stephen Vance
Cc: perforce-user <at> perforce.com
Subject: Re: [p4] Syncing all files to one folder

I don't think there is a limit on the client spec size, we have some
VERY large ones.
(Continue reading)

Permalink | Reply | 16 comments |
headers
Tony Whitley (Hotmail | 3 Jun 2008 15:44
Picon
Favicon

Re: [p4] Syncing all files to one folder

Sorry, I think what I tried was

//depot/.../inc/... //myworkspace/.../include/...

which works the same as

//depot/A/inc/... //myworkspace/A/include/...
//depot/B/inc/... //myworkspace/B/include/...
//depot/C/inc/... //myworkspace/C/include/...
..

not what you want.

----- Original Message ----- 
From: "Tony Whitley"
Sent: Tuesday, June 03, 2008 2:09 PM
Subject: Re: [p4] Syncing all files to one folder

>I don't think there is a limit on the client spec size, we have some VERY
> large ones.
>
> Can you use:
>
> //depot/.../inc/... //myworkspace/include/...
>
> I have tried something like that and it worked.
>
> Though you'll have to be even more careful when adding new header files!
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ivey, William | 3 Jun 2008 16:05
Picon
Favicon

Re: [p4] Syncing all files to one folder

If I recall correctly, you can force the depot path when adding
files by giving the depot-equivalent path to the file instead of
the local one.

-Wm

-----Original Message-----
From: perforce-user-bounces <at> perforce.com
[mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Stephen Vance
Sent: Tuesday, June 03, 2008 6:32 AM

//depot/A/inc/... //myworkspace/include/...
+//depot/B/inc/... //myworkspace/include/...
+//depot/C/inc/... //myworkspace/include/...

You just have to be careful when adding new header files. They will all 
go to the same place.

Steve

_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 2 comments |
headers
Atul Prasad | 3 Jun 2008 16:21
Picon

Re: [p4] Syncing all files to one folder

Hi All,

Thanks for the quick response.

 <at> Robert: There are a lot of lines already in my clientspec (my code is
rather a small part in the entire module) and i have encountered this error
where it did not allow me to add any more characters.

 <at>  Tony: As Robert said, we have to have matching wildcards on the LHS and
RHS.

The problem i have is that i have multiple modules and submodules: each
finally having an src and an inc folder. Each module has some different
levels of hierarchy.
Ideally i would have liked to do something like:
//depot/main/.../inc //myworkspace/inc

Is something similar to that possible?

On Tue, Jun 3, 2008 at 7:09 PM, Greg Whitfield <
Greg.Whitfield <at> lightworkdesign.com> wrote:

> As earlier replies have mentioned, you need to be careful with the
> wildcards. You also need to ensure that there are no duplicate filenames
> in the 100+ separate INC folders as this would not easily show up in the
> one big folder.
>
> Is there a deeper-seated problem here in the organisation of your code
> and modules that you are trying to work around?
>
(Continue reading)

Permalink | Reply | 6 comments |
headers
Jeff A. Bowles | 3 Jun 2008 18:02
Picon
Favicon

Re: [p4] Syncing all files to one folder

I think Greg is on the right track: ask the workflow questions at this
point, and determine how much of this is necessary and helpful.
The point about "explicitly map these folders" is a good idea, even if it
sounds like it is not extensible. ("You mean I'll have to re-edit the view
for every new folder?")

   - The points for doing it this way are, that you don't want new
   folders/areas without knowing about them.
   - The argument against looks like this: "you want me to re-edit that
   thing every time, for something that could be automated?"

I would remind you that any wild card that looks like
"//something/.../inc/..." can take some cpu-time to sort through. This
construct, in a protection table, can be a problem for server performance;
in a client spec, it might still be less than a bed of roses.

  -Jeff Bowles

On Tue, Jun 3, 2008 at 6:39 AM, Greg Whitfield <
Greg.Whitfield <at> lightworkdesign.com> wrote:

> As earlier replies have mentioned, you need to be careful with the
> wildcards. You also need to ensure that there are no duplicate filenames
> in the 100+ separate INC folders as this would not easily show up in the
> one big folder.
>
> Is there a deeper-seated problem here in the organisation of your code
> and modules that you are trying to work around?
>
> I was just wondering why you need to do this. If it is a deployment
(Continue reading)

Permalink | Reply | 0 comments |

Gmane