Skip to content

Home

Jump to bottom
Bret Curtis edited this page Apr 17, 2014 · 12 revisions

WildMIDI'w WIKI

Development

Rules of Engagement

  • Want to help out? Create a github account and fork a repo! Follow this guide to get started: Fork-a-Repo
  • Want to get more out of git? Another to the point guide: git - the simple guide
  • Rebasing in your own branch, when finished with branch, merge that back into it's parent branch: [Rebase Guide](https://www.atlassian.com/git/tutorial/rewriting-git-history#!rebase_
  • Branching is cheap, want to fix something in a branch created by someone else... branch it and ask branch "owner" to review it and merge it in
  • Try to avoid working directly in master and wildmidi-* branches, use branches as they are cheap (obviously not necessary for typos and other trivial things)

Linux

Just fork WildMIDI to your github, clone from that, make a branch, work in it, commit it and push to your fork on github. When you are ready, just send us a pull request and we'll review it!

You'll need:

  1. git
  2. gcc or clang
  3. cmake

OSX

Windows

For VS2010, the follow install order recommended:

  1. Visual Studio 2010 Express
  2. Windows SDK 7.1
  3. Visual Studio 2010 SP1
  4. Visual C++ 2010 SP1 Compiler Update for the Windows SDK 7.1

The Express addition only has support for x32, but with the SDK you can get x64 support.

It is also recommended to to install MSYSGIT, as it will setup your windows shell to handle a bit like unix with the same commands. http://msysgit.github.io/

You'll also need cmake: http://www.cmake.org/cmake/resources/software.html

DOS

Supported Formats

Clone this wiki locally