Include how-to-update section

[hamoid]

Also minor headline formatting to make sections more obvious.

[roymacdonald]

Hi, Thanks for this.
If anyone is using the github version I assumes that the user has fork and changed the remotes to point to its own fork, which is what you would do in order to make pull requests.
So, I would add to check

git remote -v

and see that which is the remote that is pointing to the openFrameworks github repo, and pull on that. For example, if I call this command I get the following:

origin	git@github.com:roymacdonald/openFrameworks.git (fetch)
origin	git@github.com:roymacdonald/openFrameworks.git (push)
upstream	https://github.com/openframeworks/openFrameworks.git (fetch)
upstream	https://github.com/openframeworks/openFrameworks.git (push)

Thus, it is the upstream remote which is pointing to OF's github repo, and it is from which I need to pull. In order to do so I need to call

git pull upstream master

The download dependencies is not absolutely mandatory, it is only needed when a dependency has been updated, which does not happen often, so I would add that this should be done if the local repo has not been updated in a long time.

[hamoid]

Good point @roymacdonald , I'll update it.

[hamoid]

Better now @roymacdonald ?

[roymacdonald]

Hi. sure, sorry to bother, but I would explicitly add how to add the other remote as it is super easy.

git remote add upstream git@github.com:openframeworks/openFrameworks.git

in which upstream can be any name that is not already used for a remote, thus listed on the git remote -v command

to update the project generator it is better to call git submodule update --recursive

[hamoid]

Updated.

[roymacdonald]

Great! looks good to me.

[roymacdonald]

thanks

[ofTheo]

I ran into this recently.
If you haven't pulled in the submodules you have to do this first:
git submodule update --init --recursive

[hamoid]

Added :)

[arturoc]

thanks!