SFML Installer

[Tank]

Lo-X, probably because of increased RAM demand.

Laurent, so there are still people installing a 32 bit operating system? I really wonder, because the last time I used a 32 bit Windows operating system was many many years ago. For me a 32 bit operating system is a limiting factor which can be avoided without any hassle.

And the reason why I'm asking why many people still see it as something special: I don't see a valid reason why someone who requests a 64 bit version is considered being a "pro" while someone who wants to go with 32 bit is a "valid newbie".

[eXpl0it3r]

Unfortunately there are still people using 32bit systems, but the numbers seem to decrease (click on OS) month by month and the games shipping with 64bit applications are rising - for some I guess due to RAM usage.

Personally I'd like to just ignore 32bit and fully develop for x64, but as soon as you do so, you'll end up with at least one guy asking for a 32bit application and since one doesn't want to exclude others, has to use a 32bit compiler again.
Plus with MinGW there have been some more issues with x64.

Not to forget that Microsoft is treating 64bit as something special as well, by not providing an x64 compiler for VS express edition (iirc).

On topic: I'll see what I can do, once I get some time to look at it.

[FRex]

Why is 64 bits on Windows still treated as being so special by many people?

There is compatibility mode for 32 bit so there is not much point in caring unless you need tons of memory(which is pro).

Microsoft(apparently - see exploiter's post) doesn't provide 64 bit express, if you buy for few hundred dollars - you're a pro, if you pirate - you're evil = you don't get support for admitting it, if you have dreamspark - you SHOULD learn how to build and link yourself, that's the purpose of giving loot out for free, they are NOT gifts, they are given for learning purposes. MinGW in itself is tons of pain on 32 bit(can't be much better on 64, probably is worse) compared to how painless GCC is on Linux. Other compilers are for pros or cost money or both(Intel's, Borland's?).

It requires 2 builds if you want to support both (unless you abandon like 15-30% of user base and go only 64 bit), therefore you're a pro for knowing how to configure it all and ship two versions.

Articles like this surely don't help: http://www.gamedev.net/page/resources/_/technical/game-programming/managing-decoupling-part-2-polling-callbacks-and-events-r3044 when on gamedev and blogs of 'real' companies that claim to write 'good' code:

struct Callback16
{
  void (*f)(void);
  char data[12];
};

Unis, tutorials, old bad practices, etc. that neglect the 64 bit and/or assume pointer is 4 bytes don't help either.

Differences like registers, calling conventions etc. http://msdn.microsoft.com/en-us/library/7kcdt6fy.aspx don't seem like something non pro cares about..

[Laurent]

Not to forget that Microsoft is treating 64bit as something special as well, by not providing an x64 compiler for VS express edition (iirc).

They do. The 64 bits MSVC version of SFML is not produced by pirated software

[FRex]

They do only provide 32 bit or they do provide 64 bit too?
Also you already once stated you use(d) professional, I hope SFML wasn't built with pirated software back then either.

[eXpl0it3r]

They do. The 64 bits MSVC version of SFML is not produced by pirated software

It seems to exist and maybe it works flawless with the newer versions, but it seems to have been a pain in the past (2008, 2010, ...).

[Laurent]

They do only provide 32 bit or they do provide 64 bit too?

They provide both.

It seems to exist and maybe it works flawless with the newer versions, but it seems to have been a pain in the past (2008, 2010, ...).

It works for 2010 Express too. My VS 2008 is a professional version, so I don't know about the Express one.

[Tank]

There is compatibility mode for 32 bit so there is not much point in caring unless you need tons of memory(which is pro).

There's a compatibility mode for "everything", I don't think that's a valid reason to not do something "new". Only pros need much memory? Why?

That you can use VS Express to indeed build 64 bit binaries has been said already. Other than that, you can get a trial version of VS which is able to build 64 bit binaries. Students get the Pro editions for free. Other compilers support 64 bit binaries out of the box. Clicking on "64 bit" is definitely not what only "pros" are capable of.

if you buy for few hundred dollars - you're a pro

I don't see how buying something makes you a pro...

Other compilers are for pros[...]

Why?

It requires 2 builds if you want to support both (unless you abandon like 15-30% of user base and go only 64 bit), therefore you're a pro for knowing how to configure it all and ship two versions.

It's what a developer does?! Maybe it's harder for "non-pros" to build 32 bit stuff because they find it logical to choose 64 bit because their operating system says so?

I don't know what you are trying to say with your pointer size nonsense or registers and calling conventions. We are talking about compiling for a target architecture, which often is 1 configuration setting (like a checkbox in SFML Installer), not building an assembler.

Personally I think 32/64 options make sense in a program like SFML Installer, just like you have static, dynamic, release and debug options.

[Lo-X]

It requires 2 builds if you want to support both (unless you abandon like 15-30% of user base and go only 64 bit), therefore you're a pro for knowing how to configure it all and ship two versions.

Perhaps I miss something here but cross compilation (from 64b to 32b) is very easy to do, why only pro can do it ? With GCC I just have to have 32b libs and add a flag at compilation, any developper can do it.

I don't know about adding the 32b checkbox to the software, I always compile myself SFML to have control (plus I think it's much easier than pre-compiled than often don't work on Ubuntu due to libglew issues we don't care about in this post), so my opinion is maybe corrupted when I say I agree with Tank about it.

I think that letting the user the choice is always better. If he doesn't know what that is, he doesnt tuch it.

Having said that, I understand if Binary don't want to do it, after all he does what he wants with its program :p

[or75]

why ?

[binary1248]

Just for you, I updated SFMLInstaller with the newest versions of all libraries and a few fixes .

Here you go: SFMLInstaller.exe

[feliwir]

i got the same error like or75, but with ur newest executable i now get:
SFNUL Error: Certificate verification failed (specified REQUIRED), clos
ction.
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable
Required extension SGIS_texture_edge_clamp unavailable

inside a never ending loop

[binary1248]

Yeah... maybe it is simpler to just download a nightly build . I didn't intend to actively support SFMLInstaller more than a few months, and SFML's build process has gotten much easier since then (it will get even easier in the future), so SFMLInstaller really has less of a purpose now. In the end, it does the same that you would be able to do yourself with 10 clicks...

Like I said, just head over to http://nightlybuilds.ch/project/show/1/SFML and grab the latest build (green) of SFML for your compiler.