Hello there! This guide looks really nice although it's a little bit old. I have a few questions for you:
- How do packages that need compilation (such as numpy) behave in this guide? Those are probably removed completely too if I'm right (e.g.
.so would crash the app on different machine). Therefore, does this guide force a user of such package to manually install required packages with pip or how does it work?
- A similar question for packages of
.deb file: What everything is listed for a simple
pong/touchtracer there as required to install.
vagrant looks good, but this probably works on linux only, which for users of Kivy VM means having VM inside of VM. Would you mind customizing the guide so that it'd be easier for Windows users using Kivy VM? (stripping some instructions would be probably enough)- Kivy now uses SDL2 as a provider, not pygame. There's a guide for Windows with PyInstaller, so upgrading the guide should be easy.
If you think you can convert the guide to SDL2 and make it simplier for Windows users, please do make a pull request to Kivy documentation (you could ping me if you'd have a problem with docs).
If it seems too much for you, I'd like to ask you: Can I copy+edit the guide to include it as a packaging guide such as other that are available in kivy docs? If so, under what conditions?
Hello there! This guide looks really nice although it's a little bit old. I have a few questions for you:
.sowould crash the app on different machine). Therefore, does this guide force a user of such package to manually install required packages withpipor how does it work?.debfile: What everything is listed for a simplepong/touchtracer there as required to install.
vagrantlooks good, but this probably works on linux only, which for users of Kivy VM means having VM inside of VM. Would you mind customizing the guide so that it'd be easier for Windows users using Kivy VM? (stripping some instructions would be probably enough)If you think you can convert the guide to SDL2 and make it simplier for Windows users, please do make a pull request to Kivy documentation (you could ping me if you'd have a problem with docs).
If it seems too much for you, I'd like to ask you: Can I copy+edit the guide to include it as a packaging guide such as other that are available in kivy docs? If so, under what conditions?