mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-07-13 02:17:01 +02:00
Merge bitcoin/bitcoin#30741: doc: update documentation and scripts related to build directories
6a68343ffb
doc: Prepend 'build/' to binary paths under 'src/' in docs (Lőrinc)91b3bc2b9c
doc: Update documentation generation example in developer-notes.md (Lőrinc) Pull request description: In [the other readmes](6ce50fd9d0/src/test/README.md (L19)
) we've provided a default build directory instead, unified the `developer-notes.md` to specify it explicitly. In the next commit I've used this default to go over each reference to our binaries and changed their in-source references to the build directory. Some of these changes were in example outputs - I haven't validated that the outputs are still the same. I haven't modified the build folders in the devtools. ACKs for top commit: maflcko: review ACK6a68343ffb
pablomartin4btc: ACK6a68343ffb
fanquake: ACK6a68343ffb
- we still need to followup with other scripts/devtools, and likely unify what we are doing in some way, but this is an improvement. Tree-SHA512: 905d9c68cafe1e405e98d6aa089d7a36a34c9e03403df5c67ac2c9a98cfa54a0305b647cb92247dcb9f49e9b509a8ba88367392b95618c67059684c67b6c36fb
This commit is contained in:
@ -338,9 +338,10 @@ Recommendations:
|
||||
|
||||
### Generating Documentation
|
||||
|
||||
The documentation can be generated with `cmake --build <build_dir> --target docs`.
|
||||
The resulting files are located in `<build_dir>/doc/doxygen/html`; open
|
||||
`index.html` in that directory to view the homepage.
|
||||
Assuming the build directory is named `build`,
|
||||
the documentation can be generated with `cmake --build build --target docs`.
|
||||
The resulting files will be located in `build/doc/doxygen/html`;
|
||||
open `index.html` in that directory to view the homepage.
|
||||
|
||||
Before building the `docs` target, you'll need to install these dependencies:
|
||||
|
||||
@ -467,11 +468,11 @@ which includes known Valgrind warnings in our dependencies that cannot be fixed
|
||||
in-tree. Example use:
|
||||
|
||||
```shell
|
||||
$ valgrind --suppressions=contrib/valgrind.supp src/test/test_bitcoin
|
||||
$ valgrind --suppressions=contrib/valgrind.supp build/src/test/test_bitcoin
|
||||
$ valgrind --suppressions=contrib/valgrind.supp --leak-check=full \
|
||||
--show-leak-kinds=all src/test/test_bitcoin --log_level=test_suite
|
||||
$ valgrind -v --leak-check=full src/bitcoind -printtoconsole
|
||||
$ ./test/functional/test_runner.py --valgrind
|
||||
--show-leak-kinds=all build/src/test/test_bitcoin --log_level=test_suite
|
||||
$ valgrind -v --leak-check=full build/src/bitcoind -printtoconsole
|
||||
$ ./build/test/functional/test_runner.py --valgrind
|
||||
```
|
||||
|
||||
### Compiling for test coverage
|
||||
|
Reference in New Issue
Block a user