Find on Site
Coding Tips for Linux and Windows
The following information is a variation on that found in the repository at gtk/windows/DEVELOPING.txt. Check that file for the latest updates.
- The below assumes you are presently in the directory bibledit/gtk
- We are using git, and we encourage you to use it with branching. This means that you will do a few things to set up git. For example:
- git config --global user.email "firstname.lastname@example.org"
- git config --global user.name "Your Name"
- git config --global pull.rebase true
- You can omit --global on the last command if you want to change the local .git/config instead of your global ~/.gitconfig
- Create a branch that will contain your bug fix or feature: git checkout -b your-bug-or-feature-name
- Make your code changes; compile; test; repeat until satisfied
- Commit your changes to your local repository: git commit -a -m "Descriptive message about your-bug-or-feature"
- Switch back to the master branch: git checkout master
- Get any changes to the repository since you've been "gone": git pull
- Merge your changes into the main line: git merge your-bug-or-feature-name
- Compile; test; repeat until satisfied
- At this point you would normally push your changes up to the remote repository. But not just anyone has rights to do that. So you have to send the changes to the dev team and we will integrate them if they are good. Contact us for how to do that.
- After everything on your bug or feature is done, you delete that branch: git branch -d your-bug-or-feature-name
- Repeat this process until the Lord returns!
- Every once in a while you will probably have to do some spring cleaning: make clean; make