Getting started

From vice-emu
Revision as of 10:24, 17 April 2016 by Gpz (talk | contribs)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

The purpose of this page is to give a quick introduction to people who want to support the development of VICE in one way or another.

New Developers Wanted

downloading a nightly build

Get a fresh build of WinVice here. Unofficial nightly builds for debian can be found here.

reporting bugs

For various reasons we prefer bugs being reported only through the bug tracker on sourceforge. This allows us to manage them within reasonable resources. Unfortunately you will have to create yourself an account on sourceforge to do this - we are sorry for that, but we can't handle all the spam that would quickly appear when we remove this requirement. Before reporting bugs you may want to have a look at the list of known issues

checking out the SVN repository

  • check out the current VICE source repository:
svn checkout svn://svn.code.sf.net/p/vice-emu/code/trunk trunk
or when you already have an account with write access:
svn checkout --username=YOURUSERNAME svn+ssh://YOURUSERNAME@svn.code.sf.net/p/vice-emu/code/trunk trunk
  • check out the current VICE test programs repository:
svn checkout svn://svn.code.sf.net/p/vice-emu/code/trunk trunk
or when you already have an account with write access:
svn checkout --username=YOURUSERNAME svn+ssh://YOURUSERNAME@svn.code.sf.net/p/vice-emu/code/testprogs testprogs

building VICE from source

VICE can be build on various setups and operating systems - please look in the VICE source tree at vice/doc/building/ for detailed instructions. (and please let us know if these don't work for you)

Documentation for Developers

for a full list of existing documentation look here.

submit patches

We prefer patches being submitted via the Sourceforge Tracker:

in the toplevel VICE directory type

svn diff > mypatch.diff

and attach the resulting file.

Please make sure to respect the coding guidelines, and create one patch per issue - giant "all in one" patches are hard to manage properly and may be rejected.

contact the developers