Posted by Wade Walker on Jan 05, 2011; 3:18pm
URL: https://forum.jogamp.org/Build-errors-on-Solaris-tp2151661p2199110.html

Hi Attila! Thanks so much for this fix, it's nice to know that things will still build on Solaris with so few changes

A pull request is much easier for Sven to deal with, so here's a quick instruction on how to make one. I'm assuming you've already got git installed since your build is working.

1. Create a free GitHub account at http://github.com/

2. Generate new (or use existing) SSH keys
  - To generate, see http://help.github.com/msysgit-key-setup/
  - If you already have RSA keys in .ssh, you can just enter one of them into GitHub
  - To test, type "ssh git@github.com" and enter your passphrase at
    the prompt. It should say "You've successfully authenticated, but GitHub does not provide shell
    access. Connection to github.com closed."

3. Set your username and email in git global settings
  - git config --global user.name "Your Name"
  - git config --global user.email "someone@wherever.com"

4. Fork gluegen and jogl projects on Github
  - This gives you a place to push your changes to
  - See http://help.github.com/forking/ for instructions
  - Go to https://github.com/sgothel/gluegen, press the "Fork" button
  - Go to https://github.com/sgothel/jogl, press the "Fork" button

5. Clone gluegen and jogl locally from your forks
  - Open shell, cd to where you want your repositories, type these commands
    (they'll require your SSH passphrase)
  - git clone git@github.com:YourGitHubName/gluegen.git gluegen
  - git clone git@github.com:YourGitHubName/jogl.git jogl

6. Build the projects
  - cd gluegen/make, type "ant clean", then "ant"
  - cd jogl/make, type "ant clean", then "ant"

7. Create bug report at https://jogamp.org/bugzilla/
  - This gives you a bug number, I like to name my branches with it

8. Create branch for fix
  - cd jogl
  - git branch bug_xxx
  - git checkout bug_xxx

9. Change files, test, and commit
  - git status (shows modified files)
  - git commit -a -v (commits all modified files, lets you type commit message)

10. Push branch back to Github
  - git push origin bug_xxx

11. Send pull request on Github
  - Instructions on http://help.github.com/pull-requests/
  - Go to your project on Github
  - Switch branch to bug_xxx
  - Press "Pull Request" button
  - Type comment, check diffs
  - Press "Send pull request"

12. When your pull request is accepted, update the bug status to "Resolved" on Bugzilla!

And that's all there is to it! Just 12 easy steps