Author Topic: SFML2-Build-Package (VC++) (Read 5268 times)

Mr. X · « **on:** November 20, 2010, 01:42:47 pm »

For everyone who does not like CMake:
A nicer VC++ 2010 project file with x64-configuration (And all needed extlibs) (Its also usable for x86, of course): http://kloke-witten.dyndns.org/~philipp/downloads/SFML-Build-Paket_2.1813.0.zip
This version is for revision 1813, but it works with some newer revisions as well (I will update it if necessary)

Just extract it into the existing SFML2 folder and open the project file in /build/VC++ 2010/. The libs will appear in /lib/VC++ 2010/.

Thread in the inofficial german forum: http://forum.sfml-dev.de/index.php/topic,303.0.html

If you would like to get a x64 (and/or Itanium) compiler for VC++ 2010 Express, just install the Windows SDK 7.1

Laurent · « **Reply #1 on:** November 20, 2010, 02:06:29 pm »

Quote

For everyone who does not like CMake

CMake configuration is just a one step process, once your VS solution is generated you don't have to deal with CMake anymore. With the advantage that your VS solution is automatically updated whenever I make a modification to SFML (whereas yours is already outdated).

Mr. X · « **Reply #2 on:** November 20, 2010, 02:24:29 pm »

Should not be too outdated. An .inl file does not need to be attached to the project file.

And as soon as SFML2 is released, its less often outdated.

Laurent · « **Reply #3 on:** November 20, 2010, 02:28:58 pm »

I agree, but I still can't see anything against the CMake configuration process. It's not as if you had to live with CMake in your everyday SFML life.

Mr. X · « **Reply #4 on:** November 20, 2010, 05:37:26 pm »

The project file generated by Cmake does not contain a static configuration. The libraries are not put into the expected folder (/lib/msvc or /lib/VC++ 2010). You need to install another tool to be able to compile SFML. I "need" a x64 configuration (What is most likely the largest advantage of my makefile). On some systems, Cmake does not work (on my pc it works).
But its correct that it is not always up to date.

Laurent · « **Reply #5 on:** November 20, 2010, 07:25:27 pm »

Quote

The project file generated by Cmake does not contain a static configuration

Set BUILD_SHARED_LIBS to false.

Quote

The libraries are not put into the expected folder

There's no "expected" folder. Everyone wants a different location for the generated libraries.
The CMAKE_INSTALL_PREFIX option is made for that.

Quote

I "need" a x64 configuration (What is most likely the largest advantage of my makefile)

What's the problem with CMake?

Quote

On some systems, Cmake does not work (on my pc it works)

Which ones? I think it works on all systems that support Visual Studio.

Mr. X · « **Reply #6 on:** November 20, 2010, 08:09:10 pm »

Quote from: "Laurent"

Quote
The project file generated by Cmake does not contain a static configuration

Set BUILD_SHARED_LIBS to false.

(...)

What's the problem with CMake?

Its just painful to use it, I think.

Just think of the SFML-build-package as an option for everyone who dislikes CMake or has problems with it. Nobody is forced to use it.

Laurent · « **Reply #7 on:** November 20, 2010, 08:11:34 pm »

Quote

Nobody is forced to use it.

Sure

I'm just trying to know what's difficult, in case I can help to make it easier. I also bother you with explanations, because many users that "don't like" CMake simply didn't spend enough time with it to see how simple it is.

I understand that you don't like it and I won't try to force you to use it. It's your choice.

Mr. X · « **Reply #8 on:** November 27, 2010, 02:54:22 pm »

I now added solutions for csfml and sfml.net