10
11
12
13
14
15
16
17
18
19
20
21
22
23
|
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
|
+
|
want to compile the code themselves can use one of the
[./build.wiki | existing makefiles].
So must people do not need to be concerned with the
build complexities of Fossil. But hard-core developers who desire
a deep understanding of how Fossil is put together can benefit
from reviewing this article.
<a name="srctour"></a>
<h1>2.0 Source Code Tour</h1>
The source code for Fossil is found in the
[/dir?ci=trunk&name=src | src/] subdirectory of the
source tree. The src/ subdirectory contains all code, including
the code for the separate preprocessor programs.
|
115
116
117
118
119
120
121
122
123
124
125
126
127
128
|
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
|
+
|
The pathnames in the above command might need to be adjusted to get the
directories right. The point is that the manifest.uuid, manifest, and
VERSION files
in the root of the source tree are the three arguments and
the generated VERSION.h file appears on standard output.
<a name="preprocessing"></a>
<h1>4.0 Preprocessing</h1>
There are three preprocessors for the Fossil sources. The mkindex
and translate preprocessors can be run in any order. The makeheaders
preprocessor must be run after translate.
<h2>4.1 The mkindex preprocessor</h2>
|
234
235
236
237
238
239
240
|
236
237
238
239
240
241
242
243
244
245
246
247
|
+
+
+
+
+
|
<h1>6.0 Linkage</h1>
Fossil needs to be linked against [http://www.zlib.net | zlib]. If
the HTTPS option is enabled, then it will also need to link against
the appropriate SSL implementation. And, of course, Fossil needs to
link against the standard C library. No other libraries or external
dependences are used.
<h1>7.0 See Also</h1>
* [./tech_overview.wiki | A Technical Overview Of Fossil]
* [./adding_code.wiki | How To Add Features To Fossil]
|