330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
|
<pre><code>docker image rm THE_FOSSIL_ID THE_ALPINE_ID</code></pre>
<h2>6.0 Building on/for Android</h2>
<h3>6.1 Cross-compiling from Linux</h3>
The following instructions for building Fossil for Android,
without requiring a rooted OS, are adapted from
[https://fossil-scm.org/forum/forumpost/e0e9de4a7e | forumpost/e0e9de4a7e].
On the development machine, from the fossil source tree:
<pre><code>export CC=$NDK_PATH/toolchains/llvm/prebuilt/linux-x86_64/bin/armv7a-linux-androideabi21-clang
./configure --with-openssl=none
|
|
|
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
|
<pre><code>docker image rm THE_FOSSIL_ID THE_ALPINE_ID</code></pre>
<h2>6.0 Building on/for Android</h2>
<h3>6.1 Cross-compiling from Linux</h3>
The following instructions for building Fossil for Android via Linux,
without requiring a rooted OS, are adapted from
[https://fossil-scm.org/forum/forumpost/e0e9de4a7e | forumpost/e0e9de4a7e].
On the development machine, from the fossil source tree:
<pre><code>export CC=$NDK_PATH/toolchains/llvm/prebuilt/linux-x86_64/bin/armv7a-linux-androideabi21-clang
./configure --with-openssl=none
|
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
|
The source of such warnings is not 100% certain.
Some information about these (reportedly harmless) warnings can
be found
[https://stackoverflow.com/a/41900551 | on this StackOverflow post].
<h2>Building for Fuzz Testing</h2>
This feature is primarily intended for fossil's developers and may
change at any time. It is only known to work on Linux systems and has
been seen to work on x86/64 and ARM.
Fossil has builtin support for processing specific features using
<tt>libfuzzer</tt>. The features which can be tested this way are
|
<
|
|
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
|
The source of such warnings is not 100% certain.
Some information about these (reportedly harmless) warnings can
be found
[https://stackoverflow.com/a/41900551 | on this StackOverflow post].
<a id='fuzzer'></a>
<h2>7.0 Building for Fuzz Testing</h2>
This feature is primarily intended for fossil's developers and may
change at any time. It is only known to work on Linux systems and has
been seen to work on x86/64 and ARM.
Fossil has builtin support for processing specific features using
<tt>libfuzzer</tt>. The features which can be tested this way are
|
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
|
so may cause the fuzzer to <em>strip the --fuzztype flag</em>, leading
to it testing the wrong thing. When passing on fuzzer-specific flags
along with <tt>--fuzztype</tt>, be sure to check your system's process
list to ensure that your <tt>--fuzztype</tt> flag is there.
<a id='wasm'></a>
<h2>Building WebAssembly Components</h2>
As of version 2.19, fossil uses one component built as
[https://developer.mozilla.org/en-US/docs/WebAssembly | WebAssembly]
a.k.a. WASM. Because compiling WASM code requires non-trivial
client-side tooling, the repository includes compiled copies of these
pieces. Most Fossil hackers should never need to concern themselves
with the WASM parts, but this section describes how to for those who
|
|
|
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
|
so may cause the fuzzer to <em>strip the --fuzztype flag</em>, leading
to it testing the wrong thing. When passing on fuzzer-specific flags
along with <tt>--fuzztype</tt>, be sure to check your system's process
list to ensure that your <tt>--fuzztype</tt> flag is there.
<a id='wasm'></a>
<h2>8.0 Building WebAssembly Components</h2>
As of version 2.19, fossil uses one component built as
[https://developer.mozilla.org/en-US/docs/WebAssembly | WebAssembly]
a.k.a. WASM. Because compiling WASM code requires non-trivial
client-side tooling, the repository includes compiled copies of these
pieces. Most Fossil hackers should never need to concern themselves
with the WASM parts, but this section describes how to for those who
|