|
339
|
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
|
|
410
|
31 patch and patch the correct gcc source code. You probably want to add
|
|
|
32 m6809-unknown-none-ranlib as a symblink to /bin/true, too.
|
|
339
|
33
|
|
410
|
34 Then, you can skip the bits in the install instructions that install
|
|
|
35 "binutils" and so on. A simple "make" in the "build-6809" directory should
|
|
|
36 do. At least it does with gcc6809-4.3.4-3.
|
|
339
|
37
|
|
|
38 The exact mechanics of configuring and getting gcc to install correctly is
|
|
410
|
39 left as an exercise to the dedicated masochist. |
