Motivation
This is motivated by this comment #1778#pullrequestreview-3578687144
Rationale
It makes sense to add documentation on how to configure for CMake. I can reword if other wording is preferred
This is motivated by this comment #1778#pullrequestreview-3578687144
It makes sense to add documentation on how to configure for CMake. I can reword if other wording is preferred
348 | @@ -349,7 +349,8 @@ SECP256K1_API void secp256k1_context_destroy( 349 | * writes the message to stderr and calls abort. This default callback can be 350 | * replaced at link time if the preprocessor macro 351 | * USE_EXTERNAL_DEFAULT_CALLBACKS is defined, which is the case if the build 352 | - * has been configured with --enable-external-default-callbacks. Then the 353 | + * has been configured with --enable-external-default-callbacks or 354 | + * -DUSE_EXTERNAL_DEFAULT_CALLBACKS=1. Then the
* -DSECP256K1_USE_EXTERNAL_DEFAULT_CALLBACKS=ON. Then the
Maybe say "with --enable-external-default-callbacks (GNU Autotools) or -DSECP256K1_USE_EXTERNAL_DEFAULT_CALLBACKS=ON (CMake)."
Thanks! I updated to your suggestion in 0406cfc
ACK 0406cfc4d1d414bbc806757bb42e540bf0d8a0c1.
The PR title has to be updated as well.
ACK 0406cfc4d1d414bbc806757bb42e540bf0d8a0c1