Ah you VSS guru's
-
I had it. I'm working on a project with quite some LIB's and DLL's, where multiple modules depend on the same headers. My predecessor set up the thing the following: a) each lib/dll has it's VSS project (sounds perfect) b) shared headers are shared into a common "_Include" folder, which all modules use as additional include location (reasonable) But now... How do I share a modified header into the _Include *without* check-in and recall latest ver., and without copying manually? Thanks guys... And please don't tell me to use CVS :mad: Those who like to point out "wrong forum" are legally entitled to consider this post a flame bait
The cops still stand around and eat koeksisters - Paul Watson, The Lounge, 2002
-
I had it. I'm working on a project with quite some LIB's and DLL's, where multiple modules depend on the same headers. My predecessor set up the thing the following: a) each lib/dll has it's VSS project (sounds perfect) b) shared headers are shared into a common "_Include" folder, which all modules use as additional include location (reasonable) But now... How do I share a modified header into the _Include *without* check-in and recall latest ver., and without copying manually? Thanks guys... And please don't tell me to use CVS :mad: Those who like to point out "wrong forum" are legally entitled to consider this post a flame bait
The cops still stand around and eat koeksisters - Paul Watson, The Lounge, 2002
Apart from doing it manually, there is only one option -- some form of automated solution. If your current system doesn't handle that for you already (which it probably doesn't), you'll just have to write a little program that watches certain files/directories for changes and copies them to the desired location at each change. I don't know that one of these currently exists, but have written programs that do similar tasks. Sounds like it's time to invest a little work in a utility project. :) John
-
I had it. I'm working on a project with quite some LIB's and DLL's, where multiple modules depend on the same headers. My predecessor set up the thing the following: a) each lib/dll has it's VSS project (sounds perfect) b) shared headers are shared into a common "_Include" folder, which all modules use as additional include location (reasonable) But now... How do I share a modified header into the _Include *without* check-in and recall latest ver., and without copying manually? Thanks guys... And please don't tell me to use CVS :mad: Those who like to point out "wrong forum" are legally entitled to consider this post a flame bait
The cops still stand around and eat koeksisters - Paul Watson, The Lounge, 2002
Maybe instead of sharing a project in VSS you should share a common directory. That way, all projects point to the same _Include dir. This has drawbacks, though. You'll lose the ability of Share, Pin, Branch because there is only one Project, the _Include. Three other solutions: 1. A fileSystem monitoring tool. (c) John Fisher 2. An add-in to VC that do CI, CO and GLV automatically 3. I have to say it. It's stronger than me. Please, don't take it personally: use CVS. Crivo Automated Credit Assessment
-
Maybe instead of sharing a project in VSS you should share a common directory. That way, all projects point to the same _Include dir. This has drawbacks, though. You'll lose the ability of Share, Pin, Branch because there is only one Project, the _Include. Three other solutions: 1. A fileSystem monitoring tool. (c) John Fisher 2. An add-in to VC that do CI, CO and GLV automatically 3. I have to say it. It's stronger than me. Please, don't take it personally: use CVS. Crivo Automated Credit Assessment
-
I had it. I'm working on a project with quite some LIB's and DLL's, where multiple modules depend on the same headers. My predecessor set up the thing the following: a) each lib/dll has it's VSS project (sounds perfect) b) shared headers are shared into a common "_Include" folder, which all modules use as additional include location (reasonable) But now... How do I share a modified header into the _Include *without* check-in and recall latest ver., and without copying manually? Thanks guys... And please don't tell me to use CVS :mad: Those who like to point out "wrong forum" are legally entitled to consider this post a flame bait
The cops still stand around and eat koeksisters - Paul Watson, The Lounge, 2002
>And please don't tell me to use CVS I'm not telling you to use CVS, but you really should use cvs. ;P
-
>And please don't tell me to use CVS I'm not telling you to use CVS, but you really should use cvs. ;P
-
Are you poking fun on me??? hehe :cool:
The cops still stand around and eat koeksisters - Paul Watson, The Lounge, 2002
Oh, just a little ;) (and subconsiously I'm trying to point out what you already know... that cvs is a better product even if it doesn't have a brand name attached to it) Ritch
-
I had it. I'm working on a project with quite some LIB's and DLL's, where multiple modules depend on the same headers. My predecessor set up the thing the following: a) each lib/dll has it's VSS project (sounds perfect) b) shared headers are shared into a common "_Include" folder, which all modules use as additional include location (reasonable) But now... How do I share a modified header into the _Include *without* check-in and recall latest ver., and without copying manually? Thanks guys... And please don't tell me to use CVS :mad: Those who like to point out "wrong forum" are legally entitled to consider this post a flame bait
The cops still stand around and eat koeksisters - Paul Watson, The Lounge, 2002
First off, I have absolutely no experience with any form of version control software. However, if all you need is to make sure that a file in directory "A" is always identical to a file in directory "B" you can create an NTFS hardlink in "A" that points to the file in "B". For example, "\A\foolinked.h" would actually be the "\B\foo.h" file. Any use of "\A\foolinked.h" would always result in the indirect use of "\B\foo.h" with zero effort on your part (aside creating the initial link). Note that both files have to be on the same NTFS partition if I remember correctly. I believe there is a utility on one of the Windows CD's to do this (i.e. resource kit?). If not, I could send you some source to do this if you want to create your own command-line program. Hope this helps.
-
I had it. I'm working on a project with quite some LIB's and DLL's, where multiple modules depend on the same headers. My predecessor set up the thing the following: a) each lib/dll has it's VSS project (sounds perfect) b) shared headers are shared into a common "_Include" folder, which all modules use as additional include location (reasonable) But now... How do I share a modified header into the _Include *without* check-in and recall latest ver., and without copying manually? Thanks guys... And please don't tell me to use CVS :mad: Those who like to point out "wrong forum" are legally entitled to consider this post a flame bait
The cops still stand around and eat koeksisters - Paul Watson, The Lounge, 2002
VSS nightmares: Having source in a major revision LINKED to files in a previous major revision. Having common shared files LINKED between projects. A change in said files could BREAK entire un-related projects (and it has) that happen to be linked to the same source files. This is my life. Pity me. "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
