2,718
edits
Changes
Jump to navigation
Jump to search
Line 68:
Line 68: + + + + + + + +
Creating a new Zynthian Synth Engine (view source)
Revision as of 12:32, 13 April 2018
, 12:32, 13 April 2018→How to test
ZYNTHIN_RAISE_EXCEPTIONS=1
ZYNTHIN_RAISE_EXCEPTIONS=1
For avoiding adding/commiting every time you change/fix something, i recommend copying the files directly to your zynthian box. This will avoid polluting the git history and simplify the development/test cycle. Once your changes are tested and your code stable, you can add/commit and sync your zynthian box from your development repo, like this:
cd /zynthian/zynthian-ui
git checkout .
git pull
This will overwrite your local changes and will take the latest changes from the repo.
=== How to get the software into Zynthian(-master) ===
=== How to get the software into Zynthian(-master) ===
If it's your first developiment for zynthian, you should get familiar with git and github. I recommend start "forking" in github the repository you want to work in (zynthian-ui) and creating a "branch" for your development. When you have a stable version of your work, you should make a "pull request" from your forked github repository.
If it's your first developiment for zynthian, you should get familiar with git and github. I recommend start "forking" in github the repository you want to work in (zynthian-ui) and creating a "branch" for your development. When you have a stable version of your work, you should make a "pull request" from your forked github repository.