SFML community forums

Bindings - other languages => DotNet => Topic started by: Wibbs on October 13, 2010, 10:53:29 pm

Title: Silly problem with updating to SFML 2
Post by: Wibbs on October 13, 2010, 10:53:29 pm

Hey all,

I've been banging my head against the desk repeatedly with this, as I am certain it's a stage I'm missing when moving across to the SFML 2 files.  Everything compiles OK, but when I try to run my code I get the following error:

Unable to find an entry point named 'sfSprite_SetOrigin' in DLL 'csfml-graphics'.

This seems to me to be some kind of mismatch between the assemblies I have added references to and other files, but I can't find the basic 'How to set up SFML.net' instructions, so I can't check whether I'm doing all the steps I need to do.  

Thanks in advance for your help,

Phil

Title: Silly problem with updating to SFML 2
Post by: Laurent on October 13, 2010, 10:57:25 pm

You have to:
1. compile SFML (release static)
2. compile CSFML (release)
3. copy the CSFML DLLs to dotnet/extlibs, and wherever you need them together with the SFML.Net assemblies

Title: Silly problem with updating to SFML 2
Post by: Wibbs on October 13, 2010, 11:03:44 pm

SFML compiles fine, but trying to compile CSFML is giving me two errors:

Error   1   error C2664: 'void sf::Window::Create(sf::VideoMode,const std::string &,unsigned long,const sf::ContextSettings &)' : cannot convert parameter 1 from 'sfWindowHandle' to 'sf::VideoMode'   f:\c sharp\SFML 2\sfml2\CSFML\src\SFML\Window\Window.cpp   80   csfml-window

Error   2   error C2664: 'void sf::Window::Create(sf::VideoMode,const std::string &,unsigned long,const sf::ContextSettings &)' : cannot convert parameter 1 from 'sfWindowHandle' to 'sf::VideoMode'   f:\c sharp\SFML 2\sfml2\CSFML\src\SFML\Graphics\RenderWindow.cpp   87   csfml-graphics

Title: Silly problem with updating to SFML 2
Post by: Laurent on October 13, 2010, 11:44:10 pm

I forgot to update something with the last commit, now it should work.

Title: Silly problem with updating to SFML 2
Post by: Wibbs on October 13, 2010, 11:55:55 pm

Thanks for the quick fix - it's all working fine now :)