Skip to content
This repository has been archived by the owner on Apr 6, 2023. It is now read-only.

Setting up for development

Jump to bottom
hanrahat edited this page Jul 25, 2011 · 1 revision

Development with CoApp

Development falls into one of two categories:

CoApp Tool developer - Building the tools that make up the CoApp platform.

Package Developer/Maintainer. -

Tool Setup

  1. Visual Studio 2010 (the express version will do).
    It is recommended that you do a default install-it's known to workdefault install

  2. The Windows SDK 7.1.

  3. Git (or Mercurial with hg-git)

Setting up accounts

  1. An account on github, and the ability to check stuff in (you can use msysgit or tortoisegit , or any other git client for Windows even the Mercurial plugin hg-git, which lets you use git repositories as if they were mercurial repositories. (Note: I tried the hg-git plugin, and had to use the version here to get it to work)

  2. A current build of the CoApp tools. You can compile them yourself, or just download my latest snapshot build. Make it easy on yourself, put them in a folder that's in the %PATH%.

###Becoming a package maintainer The first thing is to get yourself added as a CoApp package-maintainer on github no worries, signing up for this isn't a lifelong commitment. If you are interested in keeping it moving over the long haul, that's great, but even if you can just do up a few projects and get them checked in, we'll figure out the long term maintenance strategy later.

In order to get added to the package maintainer group you can send me a message on github (fearthecowboy) or via email, or heck, even just send me a tweet. All I need is your github account id, and I'll add you to the group.

###Wait! Before You Begin... Since shallow-forking is intended to continually merge in changes from upstream, please keep changes to the project and its files to an absolute minimum don't do any unnecessary changes, don't reorganize the files, and don't try to rebuild a 'cleaner' build process. You only need to get it to the point where it builds a viable output. As we progress, we'll capture the data from the process and build shiny new project files that are much nicer expending extra effort now doesn't get you anywhere.

###If you run into trouble, and need help Check on IRC #coapp on freenode.net (try the webclient if you don't have IRC installed) if I'm there, I'm more than willing you help you thru the steps (and fix stuff that needs fixing), or failing that on the mailing list.

Clone this wiki locally