4 ms·
CMake Error at CMakeLists.txt:20 (find_package): By not providing "FindGLEW.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package confi
by angersock 13y ago
CMake Error at CMakeLists.txt:20 (find_package):
By not providing "FindGLEW.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "GLEW", but
CMake did not find one.
Could not find a package configuration file provided by "GLEW" with any of
the following names:
GLEWConfig.cmake
glew-config.cmake
Add the installation prefix of "GLEW" to CMAKE_PREFIX_PATH or set
"GLEW_DIR" to a directory containing one of the above files. If "GLEW"
provides a separate development package or SDK, be sure it has been
installed.
-- Configuring incomplete, errors occurred!
~
:(
(Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux)
- sown 13y agoOn ubuntu 13, I had to sudo apt-get install cmake libglew-dev xorg-dev The readme mentions this, too: sudo apt-get build-dep glfw
- angersock 13y agoRight, did all that. ;) The last step yields: Reading package lists... Done Building dependency tree Reading state information... Done E: You must put some 'source' URIs in your sources.list Debian (#!) over here. EDIT: Even after updating my /etc/apt/sources.list, and having the build-dep step run without error, I still get that original message. :(
- shmerl 13y agoIt builds and runs fine on current Debian testing.
- xmrsilentx 13y agoTry compiling cmake yourself from the latest source at: http://www.cmake.org/cmake/resources/software.html http://www.cmake.org/cmake/resources/software.html I was having the same issue on Ubuntu until I uninstalled cmake and compiled from source.
- krakensden 13y agoWelcome to the pile of busted that is CMake. If you do it for a living, you'll even get to learn their wonderful psuedo language, so you can parse through 450 lines of Find*.cmake just to figure out that all it does is check ENV_VAR0 and then fall back to a hardcoded string- even though the documentation/header claims it checks ENV_VAR1.
- csmuk 13y agoThis. CMake is another barrier to entry. what happened to a nice simple makefile? Been using just standard makefiles for literally 20 years. The only thing I do is put a checkdeps dependency on which tests for the presence of dependencies, like autoconf but without the eye poking. Have built everything from small network servers to Motif behemoths doing only that.
- zurn 13y agoYou get no (compatible) make on MSVC. More imporantly, whith nontrivial dependencies to third party libraries, self-coded makefiles just break down. Cross-platform handling of dependencies is fragile and makes drudgery. You're liable to do worse than CMake - after wasting a lot of time and energy. CMake is more an alternative to GNU autoconf and pals, with the difference that it has first class support for things like MSVC and XCode.
- csmuk 13y agoI don't build for windows so that's moot for me. Well I do but not C. I've quite happily built makefiles that work on Linux, FreeBSD, Solaris and HP/UX that aren't fragile or laborious. It just takes appropriate knowledge of the platforms. I've built some stuff on OSX (small SDL project) and it wasn't too obtuse apart from some paths. CMake, much as all of these things, works up to a point at which point it tries desperately to kill you at every available opportunity.
- blueblob 13y agoIs nmake not compatible with make? I thought that it was. I haven't programmed C/C++ on Windows at all though, so I have no experience with this.
- eroullit 13y agoFindGLEW.cmake is a standard CMake module from v2.8.10. Previous versions do not have this file thus cannot build the project. You can install a newer version of CMake or get this file from CMake git repo and copy it to /usr/share/cmake-2.8/Modules/
- morganvachon 13y agoCompiles out of the box on Slackware 14.1 64 bit. I had to run cmake in "wizard mode" (cmake -i), I kept all the defaults except changing to lib64.