From 6d4c19707ef95942e323cbdc89fbbfdbe45e7cc5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn=20Stenberg?= Date: Mon, 8 Jan 2007 23:52:01 +0000 Subject: Splitting out www git-svn-id: svn://svn.rockbox.org/rockbox/trunk@11952 a1c6a512-1295-4272-9138-f99709370657 --- www/docs/firsttime.t | 67 ---------------------------------------------------- 1 file changed, 67 deletions(-) delete mode 100644 www/docs/firsttime.t (limited to 'www/docs/firsttime.t') diff --git a/www/docs/firsttime.t b/www/docs/firsttime.t deleted file mode 100644 index 677d4e0..0000000 --- a/www/docs/firsttime.t +++ /dev/null @@ -1,67 +0,0 @@ -#define _PAGE_ First Look at Rockbox -#include "head.t" - -

First Time Guide to Rockbox Development

-

- Welcome to our humble project. -

- In order to get your hands dirty as quickly and smoothly as possible, here -follows our suggest approach! - -

Join the Rockbox Community

-

- Mail: We have a very active developers mailing list no -serious Rockbox freak can live without. -

- IRC: There's always a bunch of friendly and helpful people around in the - IRC channel. - -

Setup Your Environment

- You need a cross-compiler and linker to build the code. Pick one of these: -

- -

Get The Source

-

- Get a fresh source to build Rockbox from. We usually recommend you get the -sources fresh from the CVS repo (How to use CVS), but -you can also get a daily tarball or even the latest released source package. - -

Build Rockbox

-

- Build rockbox using your aquired sources! If you're using Linux or the -suggested cygwin approach, read How to compile -Rockbox. -

- Also note that we have put a whole lot of effort in writing simulators so -that you can build, run and try code on your host PC before you build and -download your target version. This of course requires a working compiler for -your native system. - -

Change Rockbox

-

- Before you change any code, make sure to read the contributing information if you want to have any hope of having your changes accepted. -

- Now, you fixed any bugs? You added any features? Then make a -patch and head over to the patch-tracker -and submit it. Of course, you can also check the open -bugreports and jump in and fix one of them (or possibly submit -a new bug report. - -

- Regularly checking the open feature-requests -gives a picture of what people want to see happen and what is left to add... - -

- You'll be better off with a sourceforge account for most bugreport and -feature-request work. - -#include "foot.t" -- cgit v1.1