Instead of hardcoding any values, hardcode what we think the most likely implementation is, and check that first. It was pointed out that while for example, Apple only provides libc++ and supports that for xcode, a user could install a custom environment (such as homebrew) which uses it's own copy of libstdc++, and we need to account for that. This means that a library search will be done, but only once and the result will be cached, on all systems.pull/11949/head
parent
de44455b4b
commit
9cc67b7fd1
1 changed files with 11 additions and 14 deletions
Loading…
Reference in new issue