This PR is a continuation of #31268 and applies similar changes to the minisketch
library, which addresses this comment.
Additionally, a workaround for a CMake bug has been removed.
minisketch
library directly
#31880
This PR is a continuation of #31268 and applies similar changes to the minisketch
library, which addresses this comment.
Additionally, a workaround for a CMake bug has been removed.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/31880.
See the guideline for information on the review process.
Type | Reviewers |
---|---|
ACK | theuni |
Concept ACK | purpleKarrot |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
No conflicts as of last run.
Concept NACK.
I am not a big fan of simple utility functions that group a small set of builtin cmake commands. I think they increase the cognitive load and impede knowledge transfer from one cmake project to another. (I remember a time when builtin functions like add_library
had to be wrapped and I authored many such wrappers, because there was no way of propagating interface requirements from one target to another. Those times are thankfully over since CMake version 3.0).
This change eliminates the questionable use of an `OBJECT` library and
removes the corresponding workaround for a CMake bug.
Concept NACK.
I am not a big fan of simple utility functions that group a small set of builtin cmake commands. I think they increase the cognitive load and impede knowledge transfer from one cmake project to another. (I remember a time when builtin functions like
add_library
had to be wrapped and I authored many such wrappers, because there was no way of propagating interface requirements from one target to another. Those times are thankfully over since CMake version 3.0).
Based on the above comment, I’ve concluded that this was an “Approach NACK” rather than a “Concept NACK”. Please do let me know if I am mistaken.
Reworked per feedback.
This PR provides an extended alternative to #31268,
That was merged. Is this still relevant?
Yes. It remains relevant in its updated state.
minisketch_clmul
static?
What’s the advantage here over simply making
minisketch_clmul
static?
To use the same approach across all similar cases in the project.
What’s the advantage here over simply making
minisketch_clmul
static?To use the same approach across all similar cases in the project.
Yeah, ok, agreed.
utACK 9919e92022ba61d2dc1b13b1116b56035be459a6
One less autotools-ism and CMake hack.