Kinook Software Forum

Go Back   Kinook Software Forum > Visual Build Professional > [VBP] Third Party Tools

Reply
 
Thread Tools Rate Thread Display Modes
  #1  
Old 06-30-2005, 07:18 AM
Conrad Weyns Conrad Weyns is online now
Registered User
 
Join Date: 06-30-2005
Location: Norway
Posts: 9
How to make a "dynamic" Perforce Client Spec

I am new to VBP. After 30 minutes use, I passed the point of no return :-)
The first step in my .bld is the "Perforce" tool for retrieving the latet version of a large devstudio solution.
There was no problem getting this to work.
Now I'd like to try something more advanced and share this .bld file through the Perforce depot.
This means I need to figure out a way to make a cleaver Perforce step where the local path og the .bld file somehow gets mapped to "a" or "the" correct Perforce Client Spec.
Of the 4 parameters in the Global Options, only the Port is static. The Client, Host and User need to be dynamic.
Has anyone attempted this or something similar? Any recommendations?
Conrad Weyns
Reply With Quote
  #2  
Old 06-30-2005, 11:59 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,003
Where do these dynamic values originate? The path+filename of the .bld file? You should be able to write some script expressions [1] to parse out the values, calling from each dynamic field as needed.

[1] http://www.visualbuild.com/Manual/?s...xpressions.htm
Reply With Quote
  #3  
Old 06-30-2005, 03:29 PM
Conrad Weyns Conrad Weyns is online now
Registered User
 
Join Date: 06-30-2005
Location: Norway
Posts: 9
Many thanks for your quick reply.
I have been studying all the samples and realize I need to do my homework first :-) I found one example where a Perforce client spec was created on the fly. This got me started. I use lots of client specs myself but never thought of creating one on the fly! This was much easier than what I was trying to do.

With a few Macros and a minimum of prerequisites:
1. Machine has the Perforce client installed.
2. Machine has Visual studio installed.
3. Logged in user name = a Perforce user with necessary rights.

I was able to move a .bld file around, create a client spec and get the latests source relative to the build file and start building.

Eventually, I'd like to show how one can from a singular maintained .bld file, copied to any directory on any machine with the above prerequites, build a complete release target without ever having to set up anything in particular.

So I guess I am now merely causing noise here and should stop!
Thanks again.
Conrad
Reply With Quote
Reply

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 11:05 AM.


Copyright © 1999-2023 Kinook Software, Inc.