Mercurial > hg-old > index.cgi
comparison old-trunk/extra/README @ 339:eb230fa7d28e
Prepare for migration to hg
| author | lost |
|---|---|
| date | Fri, 19 Mar 2010 02:54:14 +0000 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| 338:e7885b3ee266 | 339:eb230fa7d28e |
|---|---|
| 1 These files are extra utility type scripts that can be used for various | |
| 2 purposes. | |
| 3 | |
| 4 as | |
| 5 | |
| 6 This is a sort of front-end script that makes lwasm look approximately like | |
| 7 gnu as which is useful for using lwasm as a backend to gcc. You will | |
| 8 probably need to edit it to make it work fully. Simply put this in place | |
| 9 of whatever gcc6809 installed for "as" (in the "m6809/bin" folder in | |
| 10 "--prefix") after editing it to point to the real location of the "lwasm" | |
| 11 binary. | |
| 12 | |
| 13 | |
| 14 ld | |
| 15 | |
| 16 Similar to the "as" script above except for lwlink. | |
| 17 | |
| 18 | |
| 19 ar | |
| 20 | |
| 21 Similar to the "as" script above except for lwar. | |
| 22 | |
| 23 | |
| 24 To use these scripts, you really need to understand how to build a gcc as a | |
| 25 cross compiler. The basics are that you put the as, ld, and ar scripts | |
| 26 whereever you plan to put your cross-development binaries. Then, when | |
| 27 building the cross compiler, you tell it where the scripts are. | |
| 28 | |
| 29 You should probably name them m6809-unknown-none-{ar,as,ld} or similar | |
| 30 depending on your gcc build target. Then you'll want to get the gcc6809 | |
| 31 patch and patch the correct gcc source code. Then use a configure line | |
| 32 similar to the following: | |
| 33 | |
| 34 configure --enable-languages=c --target=m6809-coco | |
| 35 --program-prefix=m6809-coco-lwos- --enable-obsolete | |
| 36 --srcdir=/home/lost/gcc6809/src/gcc-4.3.3 --disable-threads --disable-nls | |
| 37 --disable-libssp --prefix=/usr/local/coco --with-as=/usr/local/coco/bin/as | |
| 38 --with-ld=/usr/local/coco/bin/ld --with-sysroot=/usr/local/coco | |
| 39 | |
| 40 Obviously adjust various paths to match what you're doing. | |
| 41 | |
| 42 The exact mechanics of configuring and getting gcc to install correctly is | |
| 43 left as an exercise to the dedicated masochist. |