home *** CD-ROM | disk | FTP | other *** search
-
- INSTALLATION
-
- Create an assignment called DTMP: to hold the objects
- Create an assignment called DLIB: to hold the libraries
- The DINCLUDE: assignment should exist with all the supplied includes placed
- within in.
-
- makedir dtmp:comp
- makedir dtmp:comp/lib
- cd dtmp:comp/lib
- makedir ... a whole bunch of directories, see the DMakefile ...
-
- DMake
-
-
- After the initial dmake you may remake the library at any time. KEEP A
- COPY OF THE ORIGINAL C.LIB SUPPLIED IN THE DISTRIBUTION in case you
- make a mistake... also, compiling libmake requires a c.lib to already
- exist (yours or mine).
-
- You might ask how I compiled libmake without a c.lib ... answer is that
- it compiles just fine under any compiler and that is exactly what I did
- to bootstrap DCC.
-
- --------------
-
- This is library source for DCC. c.o and x.o are copied independantly to
- /dlib. A proper link to produce a C executable with dlink requires c.o
- to be specified first, then objects, then libraries, then x.o specified
- AFTER all libraries. Libraries, in order: c.lib amiga.lib auto.lib
-
- Note that no other linker I know keeps modules sequencing intact and thus
- DCC programs will probably not run if linked with any other linker (due
- to the autoinit feature which the libraries make use of)
-
- the DCC frontend handles all of these things for you.
-
- --------------
-
- The startup code is the Amiga/ directory.... Amiga/c.a Amiga/x.a
- Amiga/main.c and Amiga/exit.c .
-
- --------------
-
- * due to a bug in Das which hasn't been fixed yet, you cannot use MOVEM
- with any addressing mode that requires an extension word (doesn't
- include the reglist of course).
-
- * You should NOT use Das for complex assembly projects. Das exists to
- assemble output from the compiler and as such is not a complete
- assembler.
-
-