Unofficial Nightly Builds

[BeautiCode]

Thank you very much.
I love the Visual c++ 13 version.

[eXpl0it3r]

Updated SFML, Thor and SFGUI builds

Since CSFML has some issues with the latest changes in SFML, the provided builds are marked as outdated and no new builds have been added.

[Demir]

Hello

I tried SFGUI-MinGW-builds-491r1-32 libs.


No such file ... compile error...
Renderer.hpp

#include <SFGUI/RendererTextureNode.hpp>

Table.hpp

#include <SFGUI/TableOptions.hpp>
#include <SFGUI/TableCell.hpp>

I think it is easy to understand for you.

My elementary solution is  taking that files from your ver..492 then  it seems worked.

[eXpl0it3r]

Looks like these files were removed/missing from the commit I guilt these binaries with, they only got re-added a few commits later (see this commit).

You could try to manually add the headers and hope it will work, otherwise upgrading to the latest nightly build and the latest compiler might be another solution.

[eXpl0it3r]

After such a long time, I finally got around to these builds again. I've removed the old ones, since they were quite old and started to junk up the space.

Updated SFML, CSFML, Thor and SFGUI

Unfortunately there seems to be some issues with CSFML for Visual Studio 2010 and 2012. Probably something with my build script. When I get time, I'll look into it, but since they are C libraries, one should also be able to use the VS 2013 ones in VS 2010/2012 projects.

[eXpl0it3r]

Updated CSFML and Thor Visual Studio builds

Figured out the build script issue for CSFML and Thor, everything should now work properly.

[Hapax]

Yay. Time for me to update to SFML 2.3! 

[Hapax]

The space in the file name in "Visual Studio" causes some trouble as the downloaded file loses everything after the space (it did for me, anyway). It's not a huge problem but it's probably something you didn't realise was happening.

[eXpl0it3r]

Arg I thought I fixed that already. 

[eXpl0it3r]

Updated all builds, added VS 2015RC builds and update MinGW Builds to GCC 5.1.0

I hope this helps all the people who've been looking for VS 2015RC builds.

[Jesper Juhl]

Not to rain on your parade; you do a great job with your builds. But:
I wonder if the SFML community might actually be better served if only source code was released.

1. Any developer worth her salt should be able to compile a library she uses.
2. We would get rid of all the annoying forum threads about "my program behaves strangely" caused by people mixing SFML downloads done with compiler A with applications compiled with compiler B.
3. The SFML team wouldn't have to maintain a build-farm for doing builds on misc platforms with misc compilers.

Seriously, if you can't manage to download, unpack and compile + link the source for a library you need, then maybe you shouldn't be writing C++ code in the first place...

[eXpl0it3r]

First off I have to say, that these builds are still unofficial ones, so the SFML Team itself has nothing to do with it.

Second I mostly agree, but unfortunately it doesn't really matter. I wish people learned how to build from source instead of being dependent on pre-built binaries, but if we did just provide the source we'd get equally as many posts about compiler issues and questions for pre-built binaries and just make more people angry at us.
Plus community members will start providing builds and if you ban builds from the forum they'll host it on some obscure site and never update it, etc. So I rather have an officially hosted binaries that we have full control over.

The "build-farm" as you put it, will in the future only generate binaries as side-effect. The main purpose is to have automated builds running on all major platforms to ensure that nothing broke.