Errors On Compilation

[Laurent]

I did. Whatever's broken is a default

You shouldn't blindly rely on SFML tutorials. I wrote them so that the forum is not spammed with beginners questions, but the truth is that one should know its tools before using a library. There are probably more complete tutorials around the internet that would help you understand Visual Studio.

[NameUser]

I did. Whatever's broken is a default

You shouldn't blindly rely on SFML tutorials. I wrote them so that the forum is not spammed with beginners questions, but the truth is that one should know its tools before using a library. There are probably more complete tutorials around the internet that would help you understand Visual Studio.

You have to understand I'm getting conflicting directions now. Gonna take yours though seeing as you made the bloody thing.

I've used VS a fair bit, I've just never had to worry about changing the bit version before, because I previously had a 32 bit system.

If you could please just tell me how to fix this, I really am itching to get back to learning and practicing.

[Laurent]

You should start by telling us what you did. At the beginning of this thread you had linker errors and then suddenly it's a platform issue.

--> how did you solve the linker errors, and what did you do to trigger this 64-bits error?

[NameUser]

I started a new project and followed it strictly off of that tutorial exploiter linked. It was pretty similar to what I did the first time. I can tell there were a few differences but I don't remember exactly what.

I got the platform errors when I finished following that and plugged in the code to test it that the tutorial gives.

[eXpl0it3r]

Mind informing me how I do this?

I guess some googling would have answered you that question but...

On the top of VS there should be a dropdown box with "Debug" (or "Release") written, next to that one there's another dropdown box with "x64"  (or "Win32") written in it. If there's "x64" then you're compiling for 64bit CPUs and you can change that by selecting "Configuration-Manager" (or similar) in the dropdown box, then a dialogbox will open, there you choose from the top right dropdown box <New...> and on the next window choose in the uppper dropdown box "Win32".

[NameUser]

I tried googling first, it's too vague of a search. I get a million results about visual studio and bit types, but none really all that helpful.

Also, that's not the problem. It's already Win32. The problem is that the "module machine type" is x64. How would I change THAT?

[eXpl0it3r]

Also, that's not the problem. It's already Win32. The problem is that the "module machine type" is x64. How would I change THAT?

Project->Settings->Linker->Advanced->Target machine or similar.

[NameUser]

Already set to x86 :|

Edit: Now here's something curious. Setting it to x64 causes the error to reverse.

Debug\main.obj : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'

How does that make any sense at all?

[Laurent]

Don't forget to "rebuild all" after such modifications.

[eXpl0it3r]

What Laurent said and you're sure you created a completly new project and didn't add stuff to the old one?

Debug\main.obj : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'

This makes actually sense since your main.obj got compiled nonetheless as x86 and now confilicts with the target machine x64.

[NameUser]

A friend helped me out with this. The error was in the compilation of SFML. I accidently compiled it as 64-bit, which led to this large variety of issues.


Regardless, thanks for all the help. One final question, could anyone link me to a safe download of MSVCR100.dll?

Thanks.

[Laurent]

Did you ever tell us that you recompiled SFML yourself? We even spoke about the 32-bit precompiled RC, and you said nothing. I think we wasted many posts in this thread...

One final question, could anyone link me to a safe download of MSVCR100.dll?

Here is what your users are supposed to install:
http://www.microsoft.com/en-us/download/details.aspx?id=5555

[eXpl0it3r]

A friend helped me out with this. The error was in the compilation of SFML. I accidently compiled it as 64-bit, which led to this large variety of issues.

Did you ever tell us that you recompiled SFML yourself? We even spoke about the 32-bit precompiled RC, and you said nothing. I think we wasted many posts in this thread...

Such things really piss me off sometimes. 

[NameUser]

Did you ever tell us that you recompiled SFML yourself? We even spoke about the 32-bit precompiled RC, and you said nothing. I think we wasted many posts in this thread...

One final question, could anyone link me to a safe download of MSVCR100.dll?

Here is what your users are supposed to install:
http://www.microsoft.com/en-us/download/details.aspx?id=5555

Frankly I never even realized there was a precompiled version. 

When you spoke of a 32-Bit RC I assumed it was expected that I recompiled. Apologies.

One final question, could anyone link me to a safe download of MSVCR100.dll?

Here is what your users are supposed to install:
http://www.microsoft.com/en-us/download/details.aspx?id=5555

That's not why I asked. I get an error whenever I try and test a program due to lack of that. Attempting to install that offers to repair or remove it. Repair doesn't help at all. Which brings me to my original question.

And now I need MSVCR100D.dll actually.


EDIT:

Through a lot of pain and suffering, I finally have it working. Thanks for all the help. This can be closed now.