One good thing to do would be learning how to configure projects with CMake as CLion uses it too :D
Yeah, heard of clion too, I wonder how good it is.I've tried it this morning and it is still lacking a lot of features, I had hoped there would be a stronger CMake integration but you can't even tell the IDE to search for libraries as far as I can tell. You still have to write the CMake file yourself.
I'm tempted to use it, as I use both MSVC and xcode for the same code. XCode's autocomplete is slow (and I don't like XCode in general), and MSVC2012 doesn't support variadic templates. Since jetbrains support both clang and GCC and gdb, I guess it would be nice. I hope the debugger is as good as MSVC's.
I guess I'll try some day. Although I'm not sure if I'd pay for an IDE. If it's over 30 euros or 30 dollars I don't think I would buy it.
Any C++ jet brain user ?
First question, do you have to recompile SFML ? I guess not, since the SFML libs use stdlib++
Hi,There's no need to generate project files for Clion. CLion use CMakeLists.txt as project file (and stores other stuff in .clion if I recall correctly). You only need to "open project" from the IDE and select the CMakeLists.txt file I wrote in a previous post.
I cant see the clion option on cmake.
Can you teach me step by step if not too much?
Yeah, heard of clion too, I wonder how good it is.
I'm tempted to use it, as I use both MSVC and xcode for the same code. XCode's autocomplete is slow (and I don't like XCode in general), and MSVC2012 doesn't support variadic templates. Since jetbrains support both clang and GCC and gdb, I guess it would be nice. I hope the debugger is as good as MSVC's.
...(later I learned Laurent wrote a tutorial (https://github.com/SFML/SFML/wiki/Tutorial:-Compile-and-Link-SFML-with-Qt-Creator) for using SFML with Qt Creator)...This was not written by Laurent! It's a wiki, anyone can contribute. ;)
...(later I learned Laurent wrote a tutorial (https://github.com/SFML/SFML/wiki/Tutorial:-Compile-and-Link-SFML-with-Qt-Creator) for using SFML with Qt Creator)...This was not written by Laurent! It's a wiki, anyone can contribute. ;)
As for free IDEs on Windows, there's also Code::Blocks.
Btw I wouldn't advise to use TDM builds, because of the odd/bad quirks, instead MinGW Builds has personal builds and an installer over at the offical MinGW-w64 site. ;)
About TDM, I've heard about those problems, but *never ever* run into one of them myself - and I've used it a lot since Dec'13. Rock solid, not a single issue, I've been pretty happy with it. On the other hand, I once tried to install a MinGW-builds toolchain (can't recall which) and couldn't get it to work... Go figure.As long as you only use like one or maybe two libraries, things might just work fine. If you however start to seriously build up a library "system", then the TDM build will sooner than later create issues, unless you explicitly handle all the TDM quirks, as SFML does. The main issue is, that unless a build system is laid out for the TDM compilers, it can/will generate binaries that are not the way the build system intended them to be.
I've already gone way off-topic, so let me come back to the topic and I'll wrap up: I think CLion absolutely *needs* to support Windows GCC builds based on MinGW-w64, because standard MinGW32 suffers from a number of limitations at the moment that MinGW-w64 does not;I don't know if people are just too lazy or don't know the right tools, but for me it took like 30min to get CLion working with my MinGW-w64 GCC 4.9.1 build... ::)
I've already gone way off-topic, so let me come back to the topic and I'll wrap up: I think CLion absolutely *needs* to support Windows GCC builds based on MinGW-w64, because standard MinGW32 suffers from a number of limitations at the moment that MinGW-w64 does not;I don't know if people are just too lazy or don't know the right tools, but for me it took like 30min to get CLion working with my MinGW-w64 GCC 4.9.1 build... ::)
Then you spend *THIRTY MINUTES* (way too much time to configure any IDE)
So what does CLion look for? If one runs procmon if becomes obvious that CLion is trying to read from <MinGW dir>/include/_mingw.h. Since I had no old MinGW version anymore, I then had download and install it, to see what this "magic" header file holds. In the end the header is simply used to retrieve the MinGW version, all the rest can be deleted without issue.Thanks for the hint, well appreciated ;-)
With the header in place CLion now recognizes the MinGW version and finds the long existing g++.exe, gcc.exe and mingw32-make.exe.
Maybe I was a bit showing off, but mainly because it's not such a hard task if one actually tries to take on the challenge and understands their tools. ;)