SFML 2 - Cmake problems

[cristi121]

Hello!
I am trying to install SFML 2 on Codeblocks. I am following this tutorial, but Cmake is having problems building the dll's:
I managed to make it work with VS 2010, but I like Codeblocks better.

Code: [Select]


CMake Error: CMake was unable to find a build program corresponding to "MinGW Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: CMake was unable to find a build program corresponding to "MinGW Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly.
Missing variable is:
CMAKE_C_COMPILER_ENV_VAR
CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly.
Missing variable is:
CMAKE_C_COMPILER
CMake Error: Could not find cmake module file:D:/SFML/Build/CMakeFiles/CMakeCCompiler.cmake
CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly.
Missing variable is:
CMAKE_CXX_COMPILER_ENV_VAR
CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly.
Missing variable is:
CMAKE_CXX_COMPILER
CMake Error: Could not find cmake module file:D:/SFML/Build/CMakeFiles/CMakeCXXCompiler.cmake
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
Configuring incomplete, errors occurred!


What I am doing wrong?
Also, would it be possible for someone to upload the dll's somewhere?

[Svenstaro]

Set the paths to your toolchain. It can't find gcc nor make. You can do that in cmake-gui.

That, or append the location to the toolchain binaries to your PATH. If you are on Windows, you can do that in "Configure Environment Variables".

[cristi121]

I've no idea how to do any of the things you listed. Can you be a little more specific?

[Laurent]

It's explained in the tutorial...

[cristi121]

I did this, it didn't work. The errors are the same.

On Windows, if you want to use gcc (MinGW), you can temporarily add the MinGW\bin directory to the PATH and then run cmake from the command shell:
> set PATH=%PATH%;your_mingw_folder\bin
> cmake

[Laurent]

You probably did it wrong. Can you describe what you did, which as many details as possible?

[cristi121]

I wrote this in cmd, just like it says in the tutorial:

Code: [Select]


C:\Users\Cristi>set PATH=%PATH%;D:\Program Files\CodeBlocks\MinGW\bin

C:\Users\Cristi>cmake
cmake version 2.8.4


Then cmake prints about two pages of stuff (usage, option, generators).

[Laurent]

The "cmake" command is supposed to launch cmake, which I explain with more details right after this paragraph. So if you use cmake-gui, you must write "cmake-gui" instead. If you use cmake from the command line, you must execute these commands from the directory where you want to build SFML.

I know it's hard to figure out for beginners, but sometimes it's also hard for me to write a tutorial that you can just copy and paste blindly to make things work, here you need to understand a little bit what you do if you want things to work

[cristi121]

I'll just stick to 1.6, then.
Thanks for the answers.

[OniLinkPlus]

Don't stick with 1.6. ATi Radeons running on recent drivers have major issues, which will make many people unable to use anything you make with it. At least try to figure it out. I use cmake -i, which might be helpful. You can also look up CMake generators to create project files for Code::Blocks, Visual Studio, etc.

[Laurent]

I'll just stick to 1.6, then.
Thanks for the answers.

It's not complicated, really. Give it a try.
But if you don't want to learn anything and just copy and paste other people's stuff... it's up to you. I don't mean to be rude, I just don't like to see people giving up so easily without trying to understand.

[lakunar]

Maybe you should add one more screen to the tutorial which shows, what you have to do if cmake couldn't find the compiler.
Enter it yourself!
Example:
http://projectbase.pr.funpic.de/cmakeCompiler.JPG
Just enter all these paths

[Laurent]

This is not the right solution. The clean solution is to make your compiler tools available, ie. in the PATH environment variable, so that CMake can detect everything automatically.

[lakunar]

The clean solution is to make your compiler tools available

Of course you're right but it is quite useful if you have 32 & 64 bit compiler.

And before he gives up ...

[Laurent]

Of course you're right but it is quite useful if you have 32 & 64 bit compiler.

If you have several compilers, don't put them permanently in the PATH, do like the tutorial says instead.