File site/docs/build/index.md changed (mode: 100644) (index 2309237..c638d15) |
... |
... |
libreboot from the available source code. |
25 |
25 |
The following document describes how `lbmk` works, and how you can make changes |
The following document describes how `lbmk` works, and how you can make changes |
26 |
26 |
to it: [libreboot maintenance manual](../maintain/) |
to it: [libreboot maintenance manual](../maintain/) |
27 |
27 |
|
|
|
28 |
|
Release status |
|
29 |
|
============== |
|
30 |
|
|
|
31 |
|
Information about status will be reported during builds; if a board is |
|
32 |
|
marked as stable, the build proceeds without further input. If the board is |
|
33 |
|
marked anything other, a warning appears asking if you wish to proceed; to |
|
34 |
|
disable these warnings, do this before building (not recommended): |
|
35 |
|
|
|
36 |
|
export LBMK_STATUS=n |
|
37 |
|
|
|
38 |
|
In Libreboot, we specify: `stable`, `unstable`, `broken` or `untested`. |
|
39 |
|
The "unstable" marking means that the board boots mostly/entirely reliably |
|
40 |
|
annd should be safe to use, but may have a few issues, but nothing which would, |
|
41 |
|
for example, cause safety issues e.g. thermal, data reliability etc. |
|
42 |
|
|
|
43 |
|
The `broken` setting means that a given board will likely brick if flashed. |
|
44 |
|
The `untested` setting means untested. |
|
45 |
|
|
|
46 |
|
Release status is always set with regards to the current lbmk revision, on |
|
47 |
|
the theory that the current revision is being used to generate a full release. |
|
48 |
|
The setting is decided on a board-by-board basis, taking its various quirks |
|
49 |
|
and idiosynrasies into account. |
|
50 |
|
|
|
51 |
|
Multi-threaded builds |
|
52 |
|
===================== |
|
53 |
|
|
|
54 |
|
Libreboot's build system defaults to a single build thread, but you can change |
|
55 |
|
it by doing e.g. |
|
56 |
|
|
|
57 |
|
export LBMK_THREADS=4 |
|
58 |
|
|
|
59 |
|
This would make lbmk run on 4 threads. |
|
60 |
|
|
28 |
61 |
Environmental variables |
Environmental variables |
29 |
62 |
======================= |
======================= |
30 |
63 |
|
|
File site/docs/build/index.uk.md changed (mode: 100644) (index 72f97cc..69826da) |
... |
... |
libreboot з доступного джерельного коду. |
35 |
35 |
Наступний документ описує те, як працює `lbmk`, і як ви можете робити зміни |
Наступний документ описує те, як працює `lbmk`, і як ви можете робити зміни |
36 |
36 |
до нього: [керівництво обслуговування libreboot](../maintain/) |
до нього: [керівництво обслуговування libreboot](../maintain/) |
37 |
37 |
|
|
|
38 |
|
Release status |
|
39 |
|
============== |
|
40 |
|
|
|
41 |
|
Information about status will be reported during builds; if a board is |
|
42 |
|
marked as stable, the build proceeds without further input. If the board is |
|
43 |
|
marked anything other, a warning appears asking if you wish to proceed; to |
|
44 |
|
disable these warnings, do this before building (not recommended): |
|
45 |
|
|
|
46 |
|
export LBMK_STATUS=n |
|
47 |
|
|
|
48 |
|
In Libreboot, we specify: `stable`, `unstable`, `broken` or `untested`. |
|
49 |
|
The "unstable" marking means that the board boots mostly/entirely reliably |
|
50 |
|
annd should be safe to use, but may have a few issues, but nothing which would, |
|
51 |
|
for example, cause safety issues e.g. thermal, data reliability etc. |
|
52 |
|
|
|
53 |
|
The `broken` setting means that a given board will likely brick if flashed. |
|
54 |
|
The `untested` setting means untested. |
|
55 |
|
|
|
56 |
|
Release status is always set with regards to the current lbmk revision, on |
|
57 |
|
the theory that the current revision is being used to generate a full release. |
|
58 |
|
The setting is decided on a board-by-board basis, taking its various quirks |
|
59 |
|
and idiosynrasies into account. |
|
60 |
|
|
|
61 |
|
Multi-threaded builds |
|
62 |
|
===================== |
|
63 |
|
|
|
64 |
|
Libreboot's build system defaults to a single build thread, but you can change |
|
65 |
|
it by doing e.g. |
|
66 |
|
|
|
67 |
|
export LBMK_THREADS=4 |
|
68 |
|
|
|
69 |
|
This would make lbmk run on 4 threads. |
|
70 |
|
|
|
71 |
|
Environmental variables |
|
72 |
|
======================= |
|
73 |
|
|
|
74 |
|
Please read about environmental variables in [the build |
|
75 |
|
instructions](../maintain/), before running lbmk. You should set |
|
76 |
|
your variables accordingly, though you do not technically need to; some |
|
77 |
|
of them may be useful, e.g. `LBMK_THREADS` (sets the number of build threads). |
|
78 |
|
|
38 |
79 |
Environmental variables |
Environmental variables |
39 |
80 |
======================= |
======================= |
40 |
81 |
|
|