-
Notifications
You must be signed in to change notification settings - Fork 83
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
Tests fail to build in Visual Studio #434
Comments
@mwoehlke-kitware any thoughts on this? I consider GTest to be broken in KWIVER on Windows until this is addressed. |
From the README (see also #366):
|
We should not have to do this. This is a major pain. We want to be able to build this project as easily as any other project CMake-based project and not make the developers need to jump through hoops. You should not have to set your system path or launch Visual Studio from a command prompt to build KWIVER. There must be some way for CMake to inject this path into the Visual Studio project file, right? |
Not to my knowledge. (At best it would require a new feature in CMake, but I seem to recall @bradking saying it is not possible.) Anyway, you will have the same problem if you try to run the tests. |
When building KWIVER in Visual Studio on Windows, the test will fail to build because GTest is required to run at build time and is not in the system path. GTest is typically provided as part of Fletch. We need a way for CMake to add the Fletch binary directory to the path for the KWIVER visual studio solution file.
The text was updated successfully, but these errors were encountered: