SFML community forums
Help => General => Topic started by: SpaceInJourney on October 02, 2016, 07:03:28 pm
-
Im asking because SFML 2.4.0 version for VC++ 2010 isn't here.
-
You have to build the latest version yourself. There have been three newer VS versions since VS 2010, as such we have dropped it for providing pre-compiled binaries.
Unless you're restricted by your company, teacher or similar, it's advised to update your VS installation as well.
-
You have to build the latest version yourself. There have been three newer VS versions since VS 2010, as such we have dropped it for providing pre-compiled binaries.
Unless you're restricted by your company, teacher or similar, it's advised to update your VS installation as well.
Actually, Im using vs 2010 because Code::Blocks version didn't work for me, and VS 2015 is functioning weird.
-
Then rather figure out what the issues are instead of jumping to different compiler (versions). ;)
-
VS 2015 is functioning weird
What do you mean exactly ? ;D
-
VS 2015 is functioning weird
What do you mean exactly ? ;D
My thoughts exactly. I regularly use VS 2013 at work, and have recently switched from VS 2015 on Windows 7 to Code::Blocks on Fedora (OK, truth be told I was on CentOS, but I recently wiped that and went with Fedora 24, so I'll need to rebuild) at home, and I haven't had any issue with any of these IDE / OS combinations.
My recommendation would be to figure out the issue, in whatever IDE you choose to use, and move forward from there. The problem is more then likely configuration, so first of all, it's unlikely that using an older version on VS will help much, and secondly, it'll be a great opportunity to learn. Every problem that you solve is a new thing that you've learned.
-
VS 2015 is functioning weird
What do you mean exactly ? ;D
That it's laggy, freezes everytike pressing a button, and I gave up using it when I failed to make a array.
Now I use VC++ 2010 and everything works great.
-
It may be better to stick to VS2015 and figure out why it acts in the way it does and fix that. The underlying problem may end up affecting something else including your programs or VS2010, eventually.
-
That it's laggy, freezes everytike pressing a button
This could be because newer versions of Visual Studio come with "hardware acceleration" support. I've also had times when fresh installs were too buggy to use until deactivating it by going to Tools > Options > Environment > General and manually disabling automatic adjust and hardware acceleration.
and I gave up using it when I failed to make a array.
If you failed to create a simple C array in VS2015, then I don't see how you could succeed in VS2010 unless you are doing something illegal in the first place that VS2010 doesn't catch.
Now I use VC++ 2010 and everything works great.
VS2010/VS2012 were also known to be rather broken and not nearly as standard conforming as the current generations of VS. As such, you are doing yourself a great disservice by keeping on looking for broken compilers until you find one that accepts potentially broken code.