Skip to content

Conversation

@rpavlik
Copy link
Member

@rpavlik rpavlik commented Jan 6, 2017

This replaces #252 - I found the remaining (ha!) bug in the FindJsonCpp script that was likely causing issues before, and some scripts have been cleaned up and "upstreamed".

@russell-taylor
Copy link
Contributor

When I try to compile from a clean (delete cache, set CMAKE_PREFIX_PATH, configure) on CMake on Windows 10 with Visual Studio 2013, I get fatal link errors saying: "cannot open file 'GLEW::GLEW-NOTFOUND.obj'. This is using a GLEW library installed in C:/usr/local.

@russell-taylor
Copy link
Contributor

It does fix the problem on Linux. Can cmake, then ccmake and refresh several times, and build against the current OSVR-Core master.

@russell-taylor
Copy link
Contributor

CMake-GUI on Windows shows GLEW_INCLUDE_DIR as C:/usr/local/include, GLEW_LIBRARY (incorrectly) as C:/Program Files/osvrRenderManager/bin/glew32.lib and GLEW_RUNTIME_LIBRARY (incorrectly) as C:/Program Files/osvrRenderManager/bin/glew32.dll. Setting them by hand to C:/usr/local/lib/x64/glew32.lib and C:/usr/local/bin/x64/glew32.dll and then re-generating did not change the linking error.

Copy link
Contributor

@russell-taylor russell-taylor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comments in main thread about issue with GLEW on Windows 10.

@russell-taylor
Copy link
Contributor

Is there a new version of these files that fixes the GLEW issue on Windows?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants