1
General / Re: SFML Hello World project
« on: Today at 01:44:11 pm »
Thanks for the reply eXpl0it3r.
Regarding the first, I was relying on the error messages
Severity Code Description Project File Line Suppression State
Error C1001 An internal error has occurred in the compiler. Project1 c:\sfml\sfml-3.0.0-windows-vc16-32-bit\sfml-3.0.0\include\sfml\system\string.hpp 1
1>Generating code
1>c:\sfml\sfml-3.0.0-windows-vc16-32-bit\sfml-3.0.0\include\sfml\system\string.hpp(102): fatal error C1001: An internal error has occurred in the compiler.
1>(compiler file 'd:\agent\_work\1\s\src\vctools\compiler\utc\src\p2\main.c', line 187)
But it does seem to move on to trying to link:
1>LINK : fatal error LNK1000: Internal error during IMAGE::BuildImage
Regarding the failure to run:
I had dowloaded both the Win32 and x64 versions of Visual C++ 16 (2019) from the SFML download page. I am using the Community version of VS 2019 if this makes a difference. I restarted Windows too, just in case.
I tripled-checked that SFML-3.0.0-windows-vc16-32-bit/SFML-3.0.0\include was added to the include paths for the win32 versions and SFML-3.0.0-windows-vc16-32-bit\SFML-3.0.0\lib to the lib paths; while for the x64 versions the include paths point to SFML-3.0.0-windows-vc16-64-bit/SFML-3.0.0\include and the lib paths to SFML-3.0.0-windows-vc16-64-bit\SFML-3.0.0\lib
For the Debug configurations, additional library inputs are sfml-graphics-d.lib;sfml-window-d.lib;sfml-system-d.lib while for the Release ones the libraries are sfml-graphics.lib;sfml-window.lib;sfml-system.lib.
I also copied all win32 dlls to the win32 executable folder and same for x64.
These steps seem pretty standard to me for using an SDK in a project, and they should work in 10 minutes top, yet... no success whatsoever. Something in my environment?
Regarding the first, I was relying on the error messages
Severity Code Description Project File Line Suppression State
Error C1001 An internal error has occurred in the compiler. Project1 c:\sfml\sfml-3.0.0-windows-vc16-32-bit\sfml-3.0.0\include\sfml\system\string.hpp 1
1>Generating code
1>c:\sfml\sfml-3.0.0-windows-vc16-32-bit\sfml-3.0.0\include\sfml\system\string.hpp(102): fatal error C1001: An internal error has occurred in the compiler.
1>(compiler file 'd:\agent\_work\1\s\src\vctools\compiler\utc\src\p2\main.c', line 187)
But it does seem to move on to trying to link:
1>LINK : fatal error LNK1000: Internal error during IMAGE::BuildImage
Regarding the failure to run:
I had dowloaded both the Win32 and x64 versions of Visual C++ 16 (2019) from the SFML download page. I am using the Community version of VS 2019 if this makes a difference. I restarted Windows too, just in case.
I tripled-checked that SFML-3.0.0-windows-vc16-32-bit/SFML-3.0.0\include was added to the include paths for the win32 versions and SFML-3.0.0-windows-vc16-32-bit\SFML-3.0.0\lib to the lib paths; while for the x64 versions the include paths point to SFML-3.0.0-windows-vc16-64-bit/SFML-3.0.0\include and the lib paths to SFML-3.0.0-windows-vc16-64-bit\SFML-3.0.0\lib
For the Debug configurations, additional library inputs are sfml-graphics-d.lib;sfml-window-d.lib;sfml-system-d.lib while for the Release ones the libraries are sfml-graphics.lib;sfml-window.lib;sfml-system.lib.
I also copied all win32 dlls to the win32 executable folder and same for x64.
These steps seem pretty standard to me for using an SDK in a project, and they should work in 10 minutes top, yet... no success whatsoever. Something in my environment?