-
Notifications
You must be signed in to change notification settings - Fork 505
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
[QUESTION] Consider reintroducing googletest to cmake dependencies? #561
Comments
+1, other guys also suffered this problem, I think we can reintroduce |
By the way could you help to finish this PR #525 ? I'm sorry I don't have the time currently. Thanks @PragmaTwice |
@ColinChamber we can delay this PR since glog0.5 remove the autoconf which would |
OK |
10 tasks
Solved in #564 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current
cmake/gtest.cmake
is confusing, especially since it contains a directory on line 38 that does not exist, so this file does not seem to provide any functionality.The project uses the system-supplied gtest, which makes it difficult to control its version. It also seems that the project does not use mechanisms such as
find_package
for gtest, but relies directly on the system header directory (e.g./usr/include
to findgtest/gest.h
) and the-lgtest
link option.I think it would be better to reintroduce googletest with fixed tag/commit hash at the cmake level (source level) using
ExternalProject
orFetchContent
. Since gtest doesn't have many translation units, it doesn't take long to compile.I'm happy to provide PRs if that sounds like a good idea.
@tisonkun
The text was updated successfully, but these errors were encountered: