20 messages in com.perforce.perforce-user[p4] branching with InstallShield ipr...| From | Sent On | Attachments |
|---|---|---|
| Christopher Chong | 07 May 2001 16:47 | |
| Jeff A. Bowles | 07 May 2001 17:34 | |
| Tom Worrell | 07 May 2001 17:51 | |
| Sheryl McKeown | 07 May 2001 18:52 | |
| Stephen Vance | 07 May 2001 22:28 | |
| Stephen Vance | 07 May 2001 22:30 | |
| Hoff, Todd | 08 May 2001 06:32 | |
| Karr, David | 08 May 2001 08:21 | |
| Shawn Campbell | 08 May 2001 08:24 | |
| Christopher Chong | 08 May 2001 10:48 | |
| Andrew Dalgleish | 13 May 2001 19:21 | |
| Ganesh Kondal | 22 May 2001 16:53 | |
| Jim Idle | 23 May 2001 12:53 | |
| Ganesh Kondal | 23 May 2001 13:20 | |
| Ganesh Kondal | 29 May 2001 12:32 | |
| Stephen Vance | 29 May 2001 13:02 | |
| Simon Green | 30 May 2001 02:22 | |
| Sheryl McKeown | 30 May 2001 10:56 | |
| Ganesh Kondal | 30 May 2001 11:01 | |
| Mike Castle | 30 May 2001 11:39 |
| Subject: | [p4] branching with InstallShield ipr file problem |
|---|---|
| From: | Tom Worrell (to...@shoretel.com) |
| Date: | 05/07/2001 05:51:23 PM |
| List: | com.perforce.perforce-user |
On Windows machines, there is a command called Subst that produces a virtual drive that is an alias for a specific path. For example, the command:
Subst T: C:\Builds\Release\1.0
would create a T: drive that was an alias for C:\Builds\Release\1.0. Then you need to simply remember to always open your IPR file from the T: drive, and any time you add a file to a file group, select files from the T: drive.
You issue the command "Subst T: /d" to remove the alias.
At least, that's how we have dealt with hard coded fully qualified paths in InstallShield.
Tom Worrell Shoreline Communications
-----Original Message----- From: Christopher Chong [mailto:CChong at aego.com] Sent: Monday, May 07, 2001 4:48 PM To: 'perforce-user at perforce.com' Subject: [p4] branching with InstallShield ipr file problem
Hi,
I currently source control our InstallShield projects in P4 but have one lingering problem - the hardcoded InstallRoot path in the project's .ipr file. The problem is when I have to branch the project - I need to go in and manually edit this file b/c IS doesn't allow a relative path or the use of an IS variable. There should be an easy solution that escapes me :( Still, I feel fortunate that I could source control IS at all!
Thanks.
--Chris
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user