Yes I did try and follow the tutorial which was written for the SFML-2.0
After many errors it finally "compiled" but would would not run and it was then I was told that the binaries were incompatible with the compiler being used.
Make sure you're following SFML tutorial for the same version you're linking against.
I started up Code::Blocks and chose an empty project that I called graphic1 and followed the instructions which were to,
Add a "main.cpp" file to your project,
which I did by File > New > File ... >
and selecting a C/C++ source File icon calling it main.cpp as instructed and pasting in the given source code.
Then I tried to build/run it and keep getting a message box,
"It seems this that this project has not been built yet."
"Do you want to build it now?"
Selecting [yes] just keeps popping up the same message box.
The error output is:
-------------- Build: Debug in graphics1 (compiler: GNU GCC Compiler)---------------
Linking stage skipped (build target has no object files to link)
Nothing to be done (all items are up-to-date).
-------------- Run: Debug in graphics1 (compiler: GNU GCC Compiler)---------------
Checking for existence: C:\SFML-2.3.2\examples\graphics1\bin\Debug\graphics1.exe
No idea what to do with that information.
This seems like main.cpp hasn't been build. Try to follow this:
http://hongouru.blogspot.sk/2012/02/s-o-l-v-e-d-codeblocks-it-seems-that.htmlIf that doesn't work, Google. If you you are not able to find the solution in 4-5 hours, then come back to the thread. One of the requirements of a good programmer is the ability to Google out (or find out otherwise) the information they need, which requires the ability to describe the problem and provide essential information. The truth usually is, that if you're having a problem with something, someone else had this problem already.
Have downloaded CMake. Can't find any exe program to start it up.
Also it appears you must buy "Mastering CMake" and "CMake training course" to even begin understand how to use it.
For starters the tutorial to use Cmake writes,
Now you are ready to run CMake. In fact there are three different ways to run it:
cmake-gui
Managed to find,
cmake-gui.1.rst file
but it doesn't run a gui for cmake when I double click it.
The point is there is one complication added to another in trying to resolve this issue which could be resolved if the SFML team provided binaries or something like the dev-pak to just run and then any program with #include SFML would just work! It is like they only want computer science graduates to use the product not old self taught hobby programmers. I used TurboC++ on my old MSDOS machine but of course back then it was easy to program the graphics hardware yourself no libraries required.
.
My gripe with SFML is it shouldn't be this hard to use the library. I don't want to have to become an expert in the developmental environment of C++ to do something as simple as using a library when simply typing #include SFML should do the trick as it does with other advanced languages.
.
Not true. I am a self-taught programmer, never went to a ComputerScience/SoftwareEngineering school of any kind and am able to link to SFML/other libs, compile it with CMake (wonderful tool, actually), etc.. I even use it for my own personal projects. It just has a learning curve you gotta get past, and then it's all a cake thing.
Programming is not just writing code. It also contains things like setting up an environment. I myself spent a week ago whole day setting up (install deps)/(download repo)/(compile repo) cycle on my VPS, using CMake and shell script. For both Windows and Linux (cross-compile). Now I just push to the repo and execute one file on VPS and I have compiled binaries for Linux and Windows on my FTP. It took me one day, but now I can use it for any SFML project I want (and with minor changes for others too).
On the other hand, if you want to make your life easier where you can, when programming, switch to Linux. That is my personal advice to you. Again, it has some learning curve, but once you're in, you never go back (except for testing your windows builds).
