Make for RISC OS
----------------

Acorn port by M.James (Use  feedback@hamble.demon.co.uk)

Suitable for gcc, and Acorn CC

Requires the following : 
-----------------------
=
UnixLib - My version is built with UnixLib 3.6e

I have used either
Acorn C v.4     cc / link
GCC   2.4.5     gcc/ ld    (Drlink)

Gzip  To UnZip

Tar to UnTar

Loads of RAM for gcc - (or use Mode 0 on a 5M RISC PC)

Building Make
-------------
Sources are provided, and in fact , you build the Makefile application

 Un-GZIP the file

 tar -xvf make_tar

Ensure you have the usual .o directory present 

There are two build files: 

 BuildMakCC  -- For Acorn C - Spits many warnings but none fatal.

 BuildMakGC  -- For GCC     - Nice & quiet

To Build the application
------------------------

Double-click the version that you want to compile with

Both build a file called !runimage.

Name the directory !pdmake

Things you must have in the !PDmake application directory:

!PDMake.!Sprites
!PDMake.!Runimage
!PDMake.!Boot
!PDMake.!Run

(you can delete the rest once you have built make )



The History of this Make Application:
-------------------------------------

1. While hunting around info-server@ukc in 1989, I came across a set of files
which claimed to be a Public Domain Make implementation. I downloaded these,
and set about ANSI-fying them. I think I am about 95% of the way there.

I then decided to make it RISC OS 'compatible', and discovered that  there is
no ?? system variable giving ' this is the path to the directory containing
the file being worked on'. Before you scream, this can of course be extracted
from the filename passed as parameter 0 when you double click the  makefile.

I have used &FE1 as the makefile type.

As you will see when you look in the !boot and !run files , you can either
type the make command into the CLI , or double click the makefile.
I have also added the -@ makefilename parameter which tells make it's
running as a double-clicked application. Then it has to get the path name of
everything by looking at the makefile path name.  


File structure
--------------

make expects the makefile to be just above the .c and .o directories.

        |
        ------------------------------------
        |             |      |        |
     makefile         c      o      thing to make
     type FE1         |      |
                   sources  objects
                                   

           
dont forget to settype makefile FE1 or settype makefile makefile -
you can have more than one makefile with different targets in the same
directory , or use it from the CLI for setting options etc.


I hope you enjoy it..  :-)

I do now I've got it going.

July 1995

This has subsequently been updated by myself, for use with GCC and UnixLib,
and tested  by Reuben Thomas, who put up with some distinctly dodgy versions. 

This version has been tested with both gcc and Acorn Cv4

It is much less stupid than AMU. In 1989 I posted a version to Acorn and
they claimed AMU would be improved. Still waiting ....

Changes from earlier versions:

I added the -v switch which makes it print what it is about to do.

I made the silent -s option the default.

The .SUFFIXES rule defines which Acorn pathnames get swapped as well as 
the usual Make meaning of this 

e.g. 

C:f.c gets turned into C:c.f

a.h   gets turned into h.a

Assuming of course that somewhere in the .SUFFIXES rule
there is a mention of .c and .h 

See the Makefile for an example.

DISCLAIMER:

THIS SOFWARE EXISTS ONLY THANKS TO THE GENEROSITY OF ANOTHER FAR MORE
COMPETENT PROGRAMMER WHO PLACED THEIR MAKE INTO THE PUBLIC DOMAIN.
                                    
NONE OF THE REALLY DIFFICULT BITS ARE MY WORK, JUST THE EVENINGS OF
FRUSTRATION GETTING IT TO GO ON THE ARCHIMEDES.

