diff options
| author |  q66 <daniel@octaforge.org> | 2020-12-25 00:42:26 +0100 |
|---|---|---|
| committer | Daniel Kolesa <daniel@octaforge.org> | 2020-12-31 23:48:57 +0100 |
| commit | 210a2823ef4ee57cdfd759df9432f402823c7eb4 (patch) | |
| tree | ed4ab57e1068e6e3086e92a7bfcdcde49223b0c2 /Manual.md | |
| parent | gcc: use consistent patch level for musl patches (diff) | |
common/build-style: add void-cross
this introduces a new build-style void-cross, which can be used
to write system crosstoolchain templates; this is to reduce the
amount of maintenance, resolve existing problems with the cross
toolchain templates and remove repeated code
Diffstat (limited to 'Manual.md')
| -rw-r--r-- | Manual.md | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/Manual.md b/Manual.md index 6481bb4ee50..4f954b840be 100644 --- a/Manual.md +++ b/Manual.md @@ -961,6 +961,16 @@ via `make_install_target`. via `configure_args`, the meson command can be overridden by `meson_cmd` and the location of the out of source build by `meson_builddir` +- `void-cross` For cross-toolchain packages used to build Void systems. You will need to +specify `cross_triplet` (corresponds to the target triplet specified in the cross profile +for the target arch), `cross_linux_arch` (the architecture name in the Linux kernel source) +and when building Go support for musl targets, also `cross_libucontext_arch` (see `libucontext` +for available ones). Optionally, `cross_gcc_skip_go` can be specified. Individual subproject +configure arguments can be specified via `cross_*_configure_args` where `*` is `binutils`, +`gcc_bootstrap` (early gcc), `gcc` (final gcc), `glibc` (or `musl`), `configure_args` is +additionally passed to both early and final `gcc`. You can also specify custom `CFLAGS` +and `LDFLAGS` for the libc as `cross_(glibc|musl)_(cflags|ldflags)`. + For packages that use the Python module build method (`setup.py` or [PEP 517](https://www.python.org/dev/peps/pep-0517/)), you can choose one of the following: |