-
Notifications
You must be signed in to change notification settings - Fork 132
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
Don't use (outdated) self-provided gtest version (especially if another version is installed already) #201
Comments
That means that things "silently" pass tests, which I'm not a huge fan of.
I guess I don't see how this is materially different from what we have currently. Either way, we are vendoring gtest. All of that said, I'm curious what problems you are having. The way that gtest is supposed to work is that you compile it alongside your code, which is exactly what we do here. So the fact that it is available elsewhere should have no affect either way on this. Some more information or reproduction steps would be helpful. |
Sorry for the late reply, I was not in office yesterday. A bit about my setup, I have a collection of libraries checked into subfolders of
This issue looks very similar to this issue: google/googletest#4061 -- i.e., having a library which self-provides an outdated version of gtest. I don't know what gtest really recommends on how to integrate it, e.g. this page recommends fetching it via Overall, this issue is not critical for me, I can for now fix my "global" gtest version to 1.11.0 (which appears to be the version you use) -- or I disable |
What would also resolve this (for me) and should not harm anyone's build (I assume), is to add a |
@clalancette Any further opinion on this? Any solution would be fine for me (if necessary, I can also provide more information on how to reproduce the issue -- and provide a PR showing that adding I could even live with having this closed as invalid and workaround it locally. |
Yes, more information on how to reproduce would be much appreciated, since I'm still struggling to understand how this could be a problem. |
I failed to produce a stand-alone MRE. It looks like I have a fork of I'll probably workaround this locally then ... |
In case someone wants to reproduce the issue, you can run the following in a previously empty folder using bash:
|
gtest was previously removed from this repository 923c05a, however got merged back later 5a729c1.
Providing a fixed version of this causes problems if a newer version is already installed.
Suggestions:
The text was updated successfully, but these errors were encountered: