Mercurial > hg-old > index.cgi
diff old-trunk/extra/README @ 339:eb230fa7d28e
Prepare for migration to hg
author | lost |
---|---|
date | Fri, 19 Mar 2010 02:54:14 +0000 |
parents | |
children |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/old-trunk/extra/README Fri Mar 19 02:54:14 2010 +0000 @@ -0,0 +1,43 @@ +These files are extra utility type scripts that can be used for various +purposes. + +as + +This is a sort of front-end script that makes lwasm look approximately like +gnu as which is useful for using lwasm as a backend to gcc. You will +probably need to edit it to make it work fully. Simply put this in place +of whatever gcc6809 installed for "as" (in the "m6809/bin" folder in +"--prefix") after editing it to point to the real location of the "lwasm" +binary. + + +ld + +Similar to the "as" script above except for lwlink. + + +ar + +Similar to the "as" script above except for lwar. + + +To use these scripts, you really need to understand how to build a gcc as a +cross compiler. The basics are that you put the as, ld, and ar scripts +whereever you plan to put your cross-development binaries. Then, when +building the cross compiler, you tell it where the scripts are. + +You should probably name them m6809-unknown-none-{ar,as,ld} or similar +depending on your gcc build target. Then you'll want to get the gcc6809 +patch and patch the correct gcc source code. Then use a configure line +similar to the following: + +configure --enable-languages=c --target=m6809-coco +--program-prefix=m6809-coco-lwos- --enable-obsolete +--srcdir=/home/lost/gcc6809/src/gcc-4.3.3 --disable-threads --disable-nls +--disable-libssp --prefix=/usr/local/coco --with-as=/usr/local/coco/bin/as +--with-ld=/usr/local/coco/bin/ld --with-sysroot=/usr/local/coco + +Obviously adjust various paths to match what you're doing. + +The exact mechanics of configuring and getting gcc to install correctly is +left as an exercise to the dedicated masochist.