-
Notifications
You must be signed in to change notification settings - Fork 38.6k
doc: update documentation and scripts related to build directories #30741
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. Code CoverageFor detailed information about the code coverage, see the test coverage report. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
00c12c6 to
84de9e3
Compare
84de9e3 to
d21f59d
Compare
d21f59d to
3a4a143
Compare
|
Why is this a draft? |
3a4a143 to
cd993bf
Compare
master wasn't stable yet, ready for review! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK cd993bfab6c06769e756ffc1d333cd9ffa705c1e, I have reviewed changes and they look OK.
The failure in the "test each commit" CI job is unrelated.
|
Can you fixup all the commits to have proper prefixes, commit messages etc. Also, I don't think putting changes into commits based on if you actually tested things on not, make that much sense. I guess that's for your own convenience so it's easier for you to can drop the changes if they happen to be broken? However it doesn't really benefit contributors, or the changelog. |
cd993bf to
4c5e58c
Compare
To correspond to the documentation style of e.g. src/test/README.md Co-authored-by: pablomartin4btc <[email protected]>
4c5e58c to
6a68343
Compare
That's also why it was a draft at first, so that I can get feedback on how to proceed with the devtools files. |
pablomartin4btc
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 6a68343
|
Concept ACK |
1 similar comment
|
Concept ACK |
|
review ACK 6a68343 |
fanquake
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 6a68343 - we still need to followup with other scripts/devtools, and likely unify what we are doing in some way, but this is an improvement.
e64b2f1 doc: cmake: prepend and explain "build/" where needed (Larry Ruane) Pull request description: This is a small follow-on to #30741, prepend `build/` to the path for `test_runner.py`. ACKs for top commit: jonatack: ACK e64b2f1 maflcko: lgtm ACK e64b2f1 tdb3: re ACK e64b2f1 Tree-SHA512: 80943d4f342987bf060adacb1c7db2e9ff8de5a6da592846ba23f230281d3a5b306162c4c86e61739a29323eaa4abf09f69f41302996d5809f448e5788a74a87
…tories a647d44 doc: update signet documentation related to build directories (Torkel Rogstad) Pull request description: While setting up my own signet I noticed that the binary paths in the documentation for this is out of date, after build artifacts moved to the `build` directory. This PR mimics what happened in #30741 ACKs for top commit: maflcko: lgtm ACK a647d44 pablomartin4btc: ACK a647d44 tdb3: Code review and light test ACK a647d44 Tree-SHA512: ac7c3806e0ff65860c41d7b7bdad538368d8a6d8d289c10f9714804f963bafd3a9658301b6697f110f5462a92826b62770963508d5eebf88bf9a0a8442d9f72d
In the other readmes we've provided a default build directory instead, unified the
developer-notes.mdto 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.