-
Notifications
You must be signed in to change notification settings - Fork 11
Development
To ensure you receive accurate and reliable hardware results while testing, I recommend developing Kano Burner on a native machine. If you prefer a virtualised environment, test the application thoroughly.
The project will require you to install a few dependencies before starting to develop.
# Install PyQt4
brew install pyqt
# Install PySmartDL, because of its own dependencies - easier this way
sudo pip install pysmartdl
# Install PyInstaller to build the project
sudo pip install pyinstaller
The application also uses the following tools which should be installed by default.
awk dd df diskutil grep gzip kill osascript pgrep
Now simply git clone the repo and happy coding!
Do not forget to run kano-burner with sudo!
Using PyInstaller and the build scripts in build/osx, the application can be packaged as a single .app bundle and will run as a normal Mac app.
There are 2 easy steps to building:
1. Change to the build directory
cd kano-burners/build
2. Run the build script
# From build run WITHOUT SUDO!
# Note that this will not work inside a sshfs
# I recommend reading the script beforehand
./build.py
You will now find the application in the folder 'kano-burner\build\apps\Kano Burner' and it will have the Kano SD card icon. You do not need the console executable or the build folder. For distribution, put the application in a .zip and upload.
NB Not recently tested To ensure you receive accurate and reliable hardware results while testing, I recommend developing Kano Burner on a native machine. If you prefer a virtualised environment, test the application thoroughly.
The project will require you to install a few dependencies before starting to develop.
# Install PyQt4
sudo apt-get install python-qt4
# Install PySmartDL, because of its own dependencies - easier this way
sudo pip install pysmartdl
The application also uses the following tools which should be installed by default.
awk dd df eject fdisk grep gzip kill mkdosfs parted pgrep umount
Now simply git clone the repo and happy coding!
Do not forget to run kano-burner with sudo!
Fedora 21 will need the following package installed python-futures.noarch
To ensure you receive accurate and reliable hardware results while testing, I recommend developing Kano Burner on a native machine. If you prefer a virtualised environment, test the application thoroughly.
The project will require you to install a few dependencies before starting to develop.
- Download from link: Python2.7.8 x32 (do not forget to tick
Add 'python' to pathduring installation) - Save file get-pip.py and run in
cmdwithpython get-pip.py - Add pip to path by running
python C:\Python27\Tools\Scripts\win_add2path.pyand restartcmd - Download the following modules from Unofficial Windows Binaries for Python Extension Packages by Christoph Gohlke:
pywin32‑219‑cp27‑none‑win32.whlfutures‑2.2.0‑py2‑none‑any.whlPyQt4‑4.11.3‑cp27‑none‑win32.whl- Microsoft Visual C++ 2008 Redistributable Package (x86)
- Install the downloaded packages with
pip install [path_to_module] - Finally, install
PyInstallerwithpip install pyinstaller - It may be required to run
python C:\Python27\Scripts\pywin32_postinstall.py -installin case of import errors because ofwin32comwhen running the burner from source
Using PyInstaller and the build scripts in build/windows, the application can be packaged as a single .exe bundle and will run as a normal Windows app.
There are 2 easy steps to building:
1. Change to kano-burners/build directory
cd kano-burners\build
2. Run the build script
# I recommend reading the script beforehand
build.py
You will now find the application in the folder kano-burner\build\apps\Kano Burner and it will have the Kano SD card icon. You do not need the console executable or the build folder. For distribution, put the application in a .zip and upload.
The environment variable KANO_BURNER_TEST_URL (eg=http://dev.kano.me/temp/burner_test.json) can be used to redirect to a server under the control of the tester. On windows this is more complex as the environment variables aren't passed through the 'sudo' equivalent, so to use this test mode you need to run in an admin she and add 'ASADMIN' to the command line.