mirror of
https://github.com/dashpay/dash.git
synced 2024-12-25 03:52:49 +01:00
Merge #16691: doc: improve depends prefix documentation
2483266c591f7b2e62df68ee2d13740a706415ec packages.md: document depends build targets (Russell Yanofsky) be27161ee4bb7cb63346f1e79fc36ce33103a635 Clarify need to specify --prefix with depends (Russell Yanofsky) Pull request description: There seems to be some confusion about exactly how to use depends, when to pass a prefix to `./configure` etc (see #16367, #16654). I've cherry-picked two of russ's commits out of #16367, as they are clear stand-alone improvements and we don't have to wait for #16367 to improve the depends documentation. ACKs for top commit: Sjors: utACK 2483266 hebasto: ACK 2483266c591f7b2e62df68ee2d13740a706415ec, I have reviewed the code and it looks OK, I agree it can be merged. jonasschnelli: ACK 2483266c591f7b2e62df68ee2d13740a706415ec Tree-SHA512: a198c288248f573519a3b0ef384626b61cc803803280af9a448c28466e3d9949bed0332af6618dac19e81c5a6e9694afa83d976b176fd13c32a6c2c3fea3fc1f
This commit is contained in:
parent
c6df9aeb85
commit
ececf49df0
@ -12,14 +12,18 @@ For example:
|
|||||||
|
|
||||||
make HOST=x86_64-w64-mingw32 -j4
|
make HOST=x86_64-w64-mingw32 -j4
|
||||||
|
|
||||||
A prefix will be generated that's suitable for plugging into Dash's
|
**Dash's configure script by default will ignore the depends output.** In
|
||||||
configure. In the above example, a dir named x86_64-w64-mingw32 will be
|
order for it to pick up libraries, tools, and settings from the depends build,
|
||||||
|
you must point it at the appropriate `--prefix` directory generated by the
|
||||||
|
build. In the above example, a prefix dir named x86_64-w64-mingw32 will be
|
||||||
created. To use it for Dash:
|
created. To use it for Dash:
|
||||||
|
|
||||||
./configure --prefix=`pwd`/depends/x86_64-w64-mingw32
|
./configure --prefix=`pwd`/depends/x86_64-w64-mingw32
|
||||||
|
|
||||||
Common `host-platform-triplets` for cross compilation are:
|
Common `host-platform-triplets` for cross compilation are:
|
||||||
|
|
||||||
|
- `i686-pc-linux-gnu` for Linux 32 bit
|
||||||
|
- `x86_64-pc-linux-gnu` for x86 Linux
|
||||||
- `x86_64-w64-mingw32` for Win64
|
- `x86_64-w64-mingw32` for Win64
|
||||||
- `x86_64-apple-darwin19` for macOS
|
- `x86_64-apple-darwin19` for macOS
|
||||||
- `arm-linux-gnueabihf` for Linux ARM 32 bit
|
- `arm-linux-gnueabihf` for Linux ARM 32 bit
|
||||||
|
@ -181,3 +181,18 @@ For us, it's much easier to just link a static `libsecondary` into a shared
|
|||||||
static or dynamic `libsecondary`, that's not our concern. With a static
|
static or dynamic `libsecondary`, that's not our concern. With a static
|
||||||
`libsecondary`, when we need to link `libprimary` into our executable, there's no
|
`libsecondary`, when we need to link `libprimary` into our executable, there's no
|
||||||
dependency chain to worry about as `libprimary` has all the symbols.
|
dependency chain to worry about as `libprimary` has all the symbols.
|
||||||
|
|
||||||
|
## Build targets:
|
||||||
|
|
||||||
|
To build an individual package (useful for debugging), following build targets are available.
|
||||||
|
|
||||||
|
make ${package}
|
||||||
|
make ${package}_fetched
|
||||||
|
make ${package}_extracted
|
||||||
|
make ${package}_preprocessed
|
||||||
|
make ${package}_configured
|
||||||
|
make ${package}_built
|
||||||
|
make ${package}_staged
|
||||||
|
make ${package}_postprocessed
|
||||||
|
make ${package}_cached
|
||||||
|
make ${package}_cached_checksum
|
||||||
|
Loading…
Reference in New Issue
Block a user