Remove legacy "./build" command from the docs

We only use ./mk now.

Signed-off-by: Leah Rowe <info@minifree.org>
master
Leah Rowe 2024-12-25 09:08:24 +00:00 committed by Leah Rowe
parent 401d544b59
commit a2b8c07b7b
4 changed files with 10 additions and 17 deletions

View File

@ -148,10 +148,6 @@ Check: `config/dependencies/` for list of supported distros.
Однак, вам потрібно буде написано свій власний сценарій для встановлення залежностей Однак, вам потрібно буде написано свій власний сценарій для встановлення залежностей
побудови. побудови.
Canoeboot Make (cbmk) автоматично виконує всі необхідні команди; наприклад,
`./build roms` автоматично виконає `./build grub`,
якщо затребувані утиліти для GRUB не збудовано, для виготовлення корисних навантажень.
В якості результату, ви тепер можете (після встановлення правильних залежностей побудови) виконати В якості результату, ви тепер можете (після встановлення правильних залежностей побудови) виконати
лише одну команду, з свіжого Git clone, для побудови образів ROM: лише одну команду, з свіжого Git clone, для побудови образів ROM:

View File

@ -87,7 +87,7 @@ XBMK\_RELEASE
If set to `y`, it signals to `script/roms` that a release is being built, If set to `y`, it signals to `script/roms` that a release is being built,
and it will honour `release="n"` in target.cfg files. You could also set this and it will honour `release="n"` in target.cfg files. You could also set this
yourself, when doing regular builds, if you wanted to test how `./build roms` yourself when doing regular builds, if you wanted to test how `./mk -b coreboot`
behaves running it in release mode. Do this if you want to: behaves running it in release mode. Do this if you want to:
export XBMK_RELEASE=y export XBMK_RELEASE=y
@ -1166,16 +1166,9 @@ Scripts in root directory of cbmk
build build
--------------- ---------------
This is the main script. Symlinks `vendor` and `update` also point to it, as This is the main build script.
does `mk`. Direct use of this script is considered deprecate, because in a
future audit, it will be removed; the `./mk` commands will be used,
exclusively, so please use only `./mk` as directed here and elsewhere.
Take any given file under `script/` and you can do: Example commands:
./build file # (THIS IS NOT A VALID COMMAND)
For example:
./mk -b coreboot ./mk -b coreboot
./mk ./mk

View File

@ -17,7 +17,11 @@ Building and Testing
Canoeboot can be built for qemu just like any other board. Canoeboot can be built for qemu just like any other board.
`./build boot roms qemu_x86_12mb` ./mk -b coreboot qemu_x86_12mb
There is also a target that has 64-but U-Boot payload:
./mk -b coreboot qemu_x86_64_12mb
In order to test the resulting roms, you must have qemu installed on the host machine. In order to test the resulting roms, you must have qemu installed on the host machine.
Test the roms by pointing qemu to the rom in bios mode. Test the roms by pointing qemu to the rom in bios mode.
@ -29,7 +33,7 @@ For example:
There is basic support for an arm64 virtual machine as well, although the payloads are not as developed as the x86 one: There is basic support for an arm64 virtual machine as well, although the payloads are not as developed as the x86 one:
./build boot roms qemu_arm64_12mb ./mk -b coreboot qemu_arm64_12mb
``` ```
qemu-system-aarch64 -bios bin/qemu_arm64_12mb/uboot_payload_qemu_arm64_12mb_libgfxinit_corebootfb.rom \ qemu-system-aarch64 -bios bin/qemu_arm64_12mb/uboot_payload_qemu_arm64_12mb_libgfxinit_corebootfb.rom \

View File

@ -21,7 +21,7 @@ and the build dependencies are installed like so, from `cbmk/` as root:
./mk dependencies debian ./mk dependencies debian
This installs everything needed for `./build boot roms`, and part of the This installs everything needed for `./mk -b coreboot`, and part of the
build process makes use of coreboot's own cross-compile toolchain. build process makes use of coreboot's own cross-compile toolchain.
[QEMU x86/ARM64 virtual machines](../misc/emulation.md) are also [QEMU x86/ARM64 virtual machines](../misc/emulation.md) are also