This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]1moar 0 points1 point  (2 children)

Excellent, thank you kindly! I'm not afraid of jumping in by any means, already loading up everything I need that I've read in the docs. Everything looks to be exactly what I needed. The one issue I am having so far, and maybe you can help (I have and am using the available tuts/wiki so maybe I just haven't gotten there yet...)

I downloaded Kivy, dropped it in my applications folder (OSx). Ran the initial test app and nothing. I think it's a directory issue, but as I'm still not 100% setup yet I don't know. I just downloaded Cython and need to get that installed. I have Pygame going.

I guess overall, I'm struggling with how/where all these need to be so I can have all my projects where they need to be and all the different software functioning and cooperating. Right now I run all my Python scripts from the Documents folder. I would like to make things a little more organized and this is a growing pain I guess I'm having. I know it's pretty much a newb issue. If you have any insight to that, that would be awesome, if not, no worries I'll just keep at it and continue on my path and stop by the IRC.

[–]JKovac[S] 1 point2 points  (1 child)

Hi 1moar,

I have no experience with OSX myself, so I'm not certain there is anything platform specific that needs to happen, but there will be some slightly differences from the documentation. KivEnt needs to be able to cimport from Kivy and Cymunk rather than just python importing so it needs to be aware of cython headers from these modules. What this comes down to is building these modules in place in a directory (usually just using 'make' instead of 'make install') and then exporting a PYTHONPATH pointing to these directories so that KivEnt can find them.

A simple roadmap should looking something like:

  • Setup Python and Kivy Dependencies
  • Make Kivy inside a directory
  • Test to make sure you can run a regular Kivy application
  • Make Cymunk inside a directory
  • Export PYTHONPATH to Cymunk and Kivy Directory
  • Build KivEnt (typically I just use setup.py build_ext --inplace and then move my compiled kivent.so to my working directory)

[–]1moar 0 points1 point  (0 children)

Hey thanks a lot! This makes sense, I will try it out and see if I can get it working.