summaryrefslogtreecommitdiffstats
path: root/firmware/README
diff options
context:
space:
mode:
authorLinus Nielsen Feltzing <linus@haxx.se>2002-07-26 14:40:06 +0000
committerLinus Nielsen Feltzing <linus@haxx.se>2002-07-26 14:40:06 +0000
commit4e9d584d015707a5092aebae5d3b8def5ea959b7 (patch)
treeb8e955968a518c26401cf62da8ee84aa3baf115d /firmware/README
parent42faf56472cbd803d4746d0d0866871c101050df (diff)
downloadrockbox-4e9d584d015707a5092aebae5d3b8def5ea959b7.tar.gz
rockbox-4e9d584d015707a5092aebae5d3b8def5ea959b7.tar.bz2
rockbox-4e9d584d015707a5092aebae5d3b8def5ea959b7.zip
Some clarifications
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@1456 a1c6a512-1295-4272-9138-f99709370657
Diffstat (limited to 'firmware/README')
-rw-r--r--firmware/README20
1 files changed, 12 insertions, 8 deletions
diff --git a/firmware/README b/firmware/README
index 30b9e09261..67261e1690 100644
--- a/firmware/README
+++ b/firmware/README
@@ -7,24 +7,28 @@
Build your own archos.mod.
-1. Check out 'firmware' and 'apps' from CVS (or possibly form a downloaded
- archive). You probably want to check out 'tools' too (to get the configure
- script if nothing else) and possibly the 'uisimulator' too (for trying out
- things on host before making target tests).
+1. Check out 'firmware', 'apps' and 'tools' from CVS (or possibly from a
+ downloaded archive). You may possibly want 'uisimulator' too (for trying
+ out things on host before making target tests).
-2. Create your own build directory. This is where all generated files will be
+2. Build the tools by running 'make' in the tools/ directory.
+
+3. Create your own build directory, preferably in the same directory as the
+ firmware/ and apps/ directories. This is where all generated files will be
put.
-3. In your build directory, run the 'tools/configure' script and enter what
+4. In your build directory, run the 'tools/configure' script and enter what
target you want to build for and if you want a debug version or not. It'll
prompt you. The debug version is for making a gdb version out of it. It is
only useful if you run gdb towards your target Archos.
-4. *ploink*. Now you have got a Makefile generated for you. Run 'make' and
+5. Make sure you have sh-elf-gcc and siblings in the PATH.
+
+6. *ploink*. Now you have got a Makefile generated for you. Run 'make' and
soon the necessary pieces from the firmware and the apps directories have
been compiled and linked.
-5. Copy the archos.mod file to your archos, reboot it and *smile*.
+7. Copy the archos.mod file to your archos, reboot it and *smile*.
Whenever the tools/configure script gets updated, you can make your makefile
updated too by running 'tools/configure update'