Unofficial Nightly Builds

[eXpl0it3r]

Would you mind sharing your batch scripts with us exploiter?
Pretty please.

I'm usually all for sharing, but there are multiple reasons I don't want to share the batch scripts directly.
If you know how to handle the command line, you essentially can write a batch script on your own. Since working with the command line is an essential step in effectively working with different applications, one should have to learn it.
Writing a batch script is also to some extend programming and since the main idea behind programming isn't strictly language specific, the process of writing a batch script adds to the overall experience in programming.
And the more rational reason is, that most of the involved code is setup specific. I've setup my applications and directories in a special way, so if I'd just give out the script, you'd still need to adapt some parts.

The batch script essentially setup the compiler environment variable, updates the source directories with git, then invokes CMake, runs the compiler, changes the CMake settings, builds, etc. and at the end everything gets automatically 7zipped.

[capz]

But if you wish so I could help you. Either by giving you SSH access to a Mac, and you take care of everything, or you give me the build script and I send the resulting binaries to you or to a server.

Well I've never developed anything with a Mac so I'm very unsure how things work there. I've a build script now for Windows (.bat) and one for Linux (.sh), but I'm not sure to what extend it would work on a Mac, but it's actually very simple although probably not the most efficient.
It probably would be better if you built them...

If Ceylo would install macports then you could just install whatever linux tools you use that way (sudo port install portname)
Mac OS X is a certified UNIX distro, so it's not that different to a linux box once you ssh in.

[didii]

How did you build the static ones for VS2012? I tried multiple times, but it never worked. I used cmake like explained in the tutorial but VS2012 did not wanted to work with those files. According to cmake I could not use BUILD_SHARED_LIBS and SFML_USE_STATIC_STD_LIBS, which seems logical. CMAKE_BUILD_TYPE was Release, but that seems logical too, then build it with VS2012 without any error (Debug and Release), setup VS2012 to work with those files (with SFML_STATIC defined) and nothing but errors.
I could try to build it again and post the errors if you wish to have a closer look.

In any case, thanks for the files now I can at least try some VS2012 to compare.

[eXpl0it3r]

How did you build the static ones for VS2012? I tried multiple times, but it never worked.

I've had no problems so far. Make sure you're using the latest CMake version (iirc 2.8.10) and then set the flags: BUILD_SHARED_LIBS=FALSE and SFML_USE_STATIC_STD_LIBS=TRUE
Builds just fine here.

I used cmake like explained in the tutorial but VS2012 did not wanted to work with those files. According to cmake I could not use BUILD_SHARED_LIBS and SFML_USE_STATIC_STD_LIBS, which seems logical. CMAKE_BUILD_TYPE was Release, but that seems logical too, then build it with VS2012 without any error (Debug and Release), setup VS2012 to work with those files (with SFML_STATIC defined) and nothing but errors.
I could try to build it again and post the errors if you wish to have a closer look.

I don't have any problems, so if you want to figure out what goes wrong on your end, you should open a new thread, since this wouldn't have anything to do with my Nightly Builds.

In any case, thanks for the files  now I can at least try some VS2012 to compare.

I'm glad, that I could help out.

[eXpl0it3r]

Updated builds to the latest commit. Added the official MinGW32 compiler.

Due to the extlibs problem with GCC 64bit builds, I've removed them for now, until a find a way to make it work.

[kaB00M]

Thank you works for vs 2012. 

Yet I have a question: only the 32x builds works, while I have a 64x. How come?

[eXpl0it3r]

Yet I have a question: only the 32x builds works, while I have a 64x. How come?

What should this mean exactly?

If you want to use x64 builds then you need to load the x64 builds. Additionally you have to switch the compiler in Visual Studio. Though as far as I know VS Express doesn't have a x64 compiler, so simply stick with the Win32 one.

[mateandmetal]

wich MinGW "distribution" do you recommend?

I´m using the official version from mingw.org
Never used TDM (It doesn´t include MSYS as far as I know)
Never heard of "rubenvb" distro

[eXpl0it3r]

Updated the Nightly Builds to the latest commit [288bc87d3a]
There might have been problems with the past TDM releases, but those should now be fixed.

wich MinGW "distribution" do you recommend?

I´m using the official version from mingw.org
Never used TDM (It doesn´t include MSYS as far as I know)
Never heard of "rubenvb" distro

Well I'd really want to use the MinGW-w64 branch since the development seems to be a bit more active and they try to build a nicer MinGW, but since they are a bit more on the experimental side, it's not as glorious as the official version.
rubenvb is actually just a guy that also makes nightly builds but from the MinGW-w64 branch, so it's more recent that the official MinGW-w64 builds.
The TDM is at the moment now definitely out of the race since the official MinGW package has been updated to GCC 4.7.2, where TDM still uses the GCC 4.7.1-2; additionally it has the bad habit for linking statically on default and causing an error when -static-libstd is defined, which is very silly and needed an adjustment from my side to get SFML even to compile correctly.

Over all now that the official MinGW features GCC 4.7.2, I would recommend that one.

[FRex]

The link to latest build commit is

[url=http://"https://github.com/SFML/SFML/commit/288bc87d3a95a1a838372f8e7d94da1a847c1fc3"][tt][288bc87d3a][/tt][/url]

which results in:
[288bc87d3a]
while it should be

[url=https://github.com/SFML/SFML/commit/288bc87d3a95a1a838372f8e7d94da1a847c1fc3][tt][288bc87d3a][/tt][/url]

that creates:
[288bc87d3a]

[eXpl0it3r]

Thanks for pointing it out, got already fixed!

New builds will get uploaded later today.

[eXpl0it3r]

Updated the Nightly Builds to the latest commit. (Go to the first page.)

If you have any problems regarding the builds or suggests, let me know!

[MorleyDev]

Cool, useful for those who are scared of building from the source (which is pretty intimidating).

I currently have a Jenkins server I fire up whenever coding that polls a bunch of git repositories (like sfml) and builds and deploys  them automatically whenever it detects changes. Let's me keep third party libraries all up to date and it's not too tricky to set up.

Do you do something similar for these? If not you could probably save yourself a lot of time :-D Could even set it up to automatically ftp the binaries onto a website so the whole process is automated...

[AlexxanderX]

So here is the latest version of SFML 2 beta but innoficially? And its an .exe or an already maked librarie( without using CMAKE)?

[eXpl0it3r]

Do you do something similar for these? If not you could probably save yourself a lot of time :-D Could even set it up to automatically ftp the binaries onto a website so the whole process is automated...

Yeah I'm aware of Jenkins (I'm using it to build the nightly builds for SFGUI), but I didn't set it up for SFML and simple wrote a few batch files for each compiler, which pull the source from git, build every version copy stuff around like I want/need to and then automatically packs it with 7zip. If I wanted to I could also upload it to the server and make changes to the website, but since I can't always be certain if the connection is stable, I don't want to directly do that.

The advantage of using my own batch files is that I can fine tune it for every compiler and don't need some partly bloated software to do the same thing. The downside is that it needs a bit more work, but I'm fine with that.

So here is the latest version of SFML 2 beta but innoficially? And its an .exe or an already maked librarie( without using CMAKE)?

I just compile the source from GitHub, pack it with 7zip, upload the archives and release them here. It's unofficial because I'm not the developer of SFML. The archives contain all the possible builds of the library (debug/release static/dynamic lib/dll etc.) with the header files, as well as all the examples (.exe) build in release and statically and the automatically generated Doxygen documentation.
So you won't have to use CMake, since you'd only need CMake if you'd compile SFML on your own.