pysfml-cython

[kolofsson]

sf.dll needs to be in the Python path. The simplest way is to put it the current directory just before you execute the program. Or you can modify the PYTHONPATH environment variable.

Or you can run python setup.py install, and it should be available for all the programs. But I would do this only after testing the binding.

sf.dll? I only got sf.pyd as a result of my compilation. I put standard c++ libraries as well as the sf.pyd in the same folder as pong.py. The compiler still can't find the sf module...

[bastien]

You're right, it's .pyd on Windows apparently. What happens if you open a command prompt, go to the path where sf.pyd is, type “python”, and then type “import sf” interactively?

[kolofsson]

You're right, it's .pyd on Windows apparently. What happens if you open a command prompt, go to the path where sf.pyd is, type “python”, and then type “import sf” interactively?

calling "python" in cmd does not work for me, I had to enter full path:

Code: [Select]


E:\pysfml2\bastienleonard-pysfml2-cython-ca7f88f\build\lib.win32-2.7>c:\Python27\python.exe
Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sf
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: DLL load failed: Nie mo┐na odnalečŠ okreťlonego modu│u.
>>>

Last line says: Can't find specified module

[bastien]

That's strange. Last try: did you also copy the DLLs that are in SFML/extlibs? (I don't see a “DLL loaded failed” message when importing a non-existing module, so my guess is that a dependency can't be loaded.)

[kolofsson]

That's strange. Last try: did you also copy the DLLs that are in SFML/extlibs? (I don't see a “DLL loaded failed” message when importing a non-existing module, so my guess is that a dependency can't be loaded.)

OMG it worked  :shock:

The pong example runs now. Also, when I type "import sf" with extlibs in the folder, it does not return error. This was one hell of a job to make this binding work. I guess it would be much easier with VC2008 or MinGW. But still, some binaries would be really appreciated and save quite some time, instead of compiling it all.

Thanks for help and feedback.

[bastien]

Yeah, I'll try to add a binary release for Windows as soon as possible, now that the binding seems to be stable. I already tried to cross-compile it, but I have trouble testing things with Wine.

[mitsuharu]

For those running Win7 64bit with 64bit Python, I've found that you must place the SFML dlls in C:/Windows/SysWow64 to get everything working.  That put me back a couple hours trying to get my Windows box the same as my Mac.

I built SFML with MinGW (much easier than trying to do it with visual studio).

[kolofsson]

Hi Bastien

A question about debugging. As we know, SFML can be compiled as Release or Debug, and for development process it is advisable to use the Debug libraries (I don't know why exactly, I guess more debug info is being produced during runtime).

Should we use the Debug libraries in PySFML too? Will it work? Is there any reason why we should/should not use them? Is compiling the bindings for Debug libraries as simple as removing the "-d" suffix from SFML lib filenames? Are you planning to include Debug libs in the binding so that there are two output files: sf.pyd and sfd.pyd?

[bastien]

I haven't tried to debug PySFML applications, just the binding itself, and the users will normally never need to do that.
I never use debuggers for Python, except for really weird cases.

Currently, I'm using SFML compiled in release mode, but I guess you can use any version you want. The only upside I can see for using a debug version is if you plan to debug the library itself, and in some cases it might be possible that some low-level bugs occur only when some compiler optimizations are activated. I think this irrelevant for Python users.

I can't see which options are provided to cython by default when it's invoked by the setup.py script, but in practice I find that it provides enough information when an error occurs.
Looking at cython's command-line options, it looks like you can only disable doc strings, or add line directives to see where the error comes from the source file. Both are probably useless for most users since I don't use doc strings.
When I'll make a stable release, I'll try the various options to see if can significantly reduce the module size, though.

In the end, if you just want to debug your application, you can probably just use whatever Python debugger you prefer. I remember that I used Winpdb for debugging multi-threaded programs. There's also the standard module pdb. Personally, I find that print statements are enough most of the time. It's not like in C where you often just get “Segmentation fault” as an error message. ;-)

[kolofsson]

Ah, very well. No special debug libs means one thing less to care about . So far my apps did not require special debugging, so I haven't really figured out what SFML debug libs do. If you say that regular python debugger will do, that's just perfect.

Well, I think I'm going to dedicate more time to learn Python and maybe start off a little project in PySFML. I'm really overwhelmed by Python philosophy . I just hope you won't get bored too soon and that you keep updating and upgrading PySFML (e.g. reference/documentation).

[bastien]

I keep updating it because people want it, don't hesitate to message me if something needs to be improved.

[bastien]

I just compiled something that looks like a Win32 module, but I can't get it to work with Wine (it tells it can't find dependent DLLs, even when they are in the current directory).
Can someone test it on Windows and tell me if it works? Here is the direct link: https://github.com/downloads/bastienleonard/pysfml2-cython/sf.pyd

[kolofsson]

I just compiled something that looks like a Win32 module, but I can't get it to work with Wine (it tells it can't find dependent DLLs, even when they are in the current directory).
Can someone test it on Windows and tell me if it works? Here is the direct link: https://github.com/downloads/bastienleonard/pysfml2-cython/sf.pyd

I will test it as soon as I get hom from work. I can see you only put sf.pyd file. It makes no difference which SFML libs I use with it? (revision / compiler). I presume that when compiling the pyd file, you needed to have the dlls present, right? Maybe it would be good to include them in the package with the binding, so that the end-user does not have to compile SFML on his own.

[kolofsson]

OK I tested your sf.pyd and it tells me that "import sf failed, module was not found". I've no idea what's wrong with your file .

I put my own sf.pyd on the web, accessible here:

http://grebocin.com/upload/sf.pyd

Also, I put the whole Pong example, with SFML dlls, extlibs, sf.pyd and main.py:

http://grebocin.com/upload/pong.zip

Perhaps this may be of help for all PySFML starters.

[bastien]

When I try your Pong example with my sf.pyd, I get this:

Code: [Select]

err:module:import_dll Library libgcc_s_sjlj-1.dll (which is needed by L"Z:\\home\\bastien\\Desktop\\pong\\sf.pyd") not found
err:module:import_dll Library libstdc++-6.dll (which is needed by L"Z:\\home\\bastien\\Desktop\\pong\\sf.pyd") not found
Traceback (most recent call last):
  File "main.py", line 9, in <module>
    import sf

Could you copy-paste here the command-lines that are issued when you build the binding? I guess I missed something to include the standard libraries.
Also, for some reason the SFML libs I cross-compiled aren't even detected by Wine.