Christian,
There is something here that should help:
http://www.abs-consulting.com/abs_consulting_triggers.html
then read about the MAKE_VERSION_ID.trigger
this adds or replaces static strings in files pre-checkin so that "ident"
and "what" commands work on objects.. In some shops I have added a second
part that removes them (post checkout) so that there is never a conflicting
merge... since you are always merging to a checked out version.
-Hope this helps
-Charles
--- VOB Corleone
"One day.. and this day may never come... I might ask you for a favor.."
A Better Solution, Inc.
----------------------------------------------------
Charles Clarke III ClearCase Consultant
A Better Solution, Inc. (770) 252-1500 x22 [phone]
50 Springridge Ct.
Newnan, Ga. 30265 (770) 252-1501 [fax]
Email:
charles@abs-consulting.com
http://www.abs-consulting.com
.At 10:05 AM 1/3/00 +0100, Christian Pendleton wrote:
>Hi!
>
>We've used the "Revstring" constant for defining a version string that can
>be displayed by using "what" on the binary file (displays the version of all
>source files that are used to create the binary file). The update of
>Revstring in the source code is done by CVS and PVCS and I'd like to get the
>same functionality in ClearCase.
>
>I started of with a trigger that updated the string on checkin (using
>$CLEARCASE_PN and _ID_STR), but that makes all merging go non-trivial. My
>next idea was to use the -D option at clearmake to expand variables in the
>code, but the $CLEARCASE_PN and _ID_STR variables are not set when you run
>clearmake.
>
>Anybody who's got a suitable solution for this?
>
>Best regards
> Christian
>
>--------------------------
>Christian O Pendleton
>AU-System AB
>tel: +46-8-7268970
>GSM: +46-70-6625418
>ICQ: 8087387
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:15 EDT