mirror of https://github.com/c-ares/c-ares.git
The current approach for disabling tests is not a good solution because it forces you to pass --disable-tests, rather than auto-detect if your system can support the tests in the first place. Many (most?) systems do not have C++11. This also causes issues when chain-building c-ares, the hosting system needs to be updated to support passing this additional flag if necessary, it doesn't seem reasonable to add this requirement which breaks compatibility. This change auto-detects if the system can build the tests and automatically disable them if it cannot. If you pass --enable-tests to configure and the system cannot build them either due to lack of system support, or because cross-compilation is being used, it will throw an appropriate error since the user indicated they really did want the tests.pull/49/head
parent
0b7a497ab7
commit
c64a374a24
1 changed files with 22 additions and 19 deletions
Loading…
Reference in new issue