summaryrefslogtreecommitdiff
path: root/src/engine/SCons/Tool/RCS.xml
blob: eb2ddac01ca770053ccdf430d5dbef018bd66898 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
<!--
Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 The SCons Foundation

This file is processed by the bin/SConsDoc.py module.
See its __doc__ string for a discussion of the format.
-->
<tool name="RCS">
<summary>
Sets construction variables for the interaction
with the Revision Control System.
</summary>
<sets>
RCS
RCS_CO
RCS_COFLAGS
RCS_COCOM
</sets>
<uses>
RCS_COCOMSTR
</uses>
</tool>

<cvar name="RCS">
<summary>
The RCS executable.
Note that this variable is not actually used
for the command to fetch source files from RCS;
see the
&cv-link-RCS_CO;
construction variable, below.
</summary>
</cvar>

<cvar name="RCS_CO">
<summary>
The RCS "checkout" executable,
used to fetch source files from RCS.
</summary>
</cvar>

<cvar name="RCS_COCOM">
<summary>
The command line used to
fetch (checkout) source files from RCS.
</summary>
</cvar>

<cvar name="RCS_COCOMSTR">
<summary>
The string displayed when fetching
a source file from RCS.
If this is not set, then &cv-link-RCS_COCOM;
(the command line) is displayed.
</summary>
</cvar>

<cvar name="RCS_COFLAGS">
<summary>
Options that are passed to the &cv-link-RCS_CO; command.
</summary>
</cvar>

<scons_function name="RCS">
<arguments signature="env">
()
</arguments>
<summary>
A factory function that
returns a Builder object
to be used to fetch source files
from RCS.
The returned Builder
is intended to be passed to the
&f-SourceCode;
function:

This function is deprecated.  For details, see the entry for the
&f-SourceCode;
function.

Examples:

<example>
env.SourceCode('.', env.RCS())
</example>

Note that
&scons;
will fetch source files
from RCS subdirectories automatically,
so configuring RCS
as demonstrated in the above example
should only be necessary if
you are fetching from
RCS,v
files in the same
directory as the source files,
or if you need to explicitly specify RCS
for a specific subdirectory.
</summary>
</scons_function>