Weird errors with sf::Shader

[mman2112]

I've decided to try out sf::shader, however when I make even the simplest of shader programs I get errors I can't make sense of. I'm not new to GLSL, I've used it in unity.

My code is the example code from the "getting started with 2d drawing" tutorial with little modification.
the code I've added (besides initializing a simple sf:RectangleShape) is the following:

Code: [Select]

const std::string fragmentShader = "void main(){}";
shader.loadFromMemory(fragmentShader, sf::Shader::Fragment);

The expected result is a fragment shader that does nothing (I had more, but tried eliminating lines to find the root issue)

I get an unexpected error message upon running the program,

Code: [Select]

Failed to complile fragment shader:
Fragment shader failed to compile with the following errors:
ERROR: 0:1 error(#132) Syntax error: "<" parse error
ERROR: error(#273) 1 compilation errors. No code  generated

Note that there is no '<' in the code, also sometimes when I run the program it has a similar error but with a '!' indicated as the syntax error.

Also, (I don't know if this could be related) when I tried loading a shader from a file it filled the console with junk text before crashing)

the full code is the attachment.
I'm using VS2013

[Hapax]

I tested your posted code and it compiles fine. Here's a screenshot of your exact code in action:


I used VS2013 with SFML 2.2 (release version).

Which version of SFML are you using? Did you build it yourself?
Is it an older version? Problem could be fixed.
Is it a newer version? Problem could have arisen since 2.2.

[binary1248]

Visual Studio has a special "debugging version" of std::string that contains extra information which it uses in debug builds. You are probably mixing a debug application and release library or vice versa. Make sure the configurations match up and your application will pass the string verbatim to SFML.

[mman2112]

Visual Studio has a special "debugging version" of std::string that contains extra information which it uses in debug builds. You are probably mixing a debug application and release library or vice versa. Make sure the configurations match up and your application will pass the string verbatim to SFML.

Thanks so much, this did the trick.