Go to the first, previous, next, last section, table of contents.
Let's summarise the steps you need to carry to get yourself
a fully-configured build tree from scratch.
-
Get your source tree from somewhere (CVS repository or
source distribution). Say you call the root directory
`myfptools' (it does not have to be called `fptools').
Make sure that you have the essential files (see Section See section Your source tree).
-
Use `lndir' or `mkshadowdir' to create a build tree.
cd myfptools
mkshadowdir . /scratch/joe-bloggs/myfptools-sun4
You probably want to give the build tree a name that
suggests its main defining characteristic (in your mind at least),
in case you later add others.
-
Change directory to the build tree. Everything is going
to happen there now.
cd /scratch/joe-bloggs/myfptools-sun4
-
Prepare for system configuration:
autoconf
(You can skip this step if you are starting from a source distribution,
and you already have `configure' and `mk/config.h.in'.)
-
Do system configuration:
./configure
-
Create the file `mk/build.mk',
adding definitions for your desired configuration options.
emacs mk/build.mk
You can make subsequent changes to `mk/build.mk' as often
as you like. You do not have to run any further configuration
programs to make these changes take effect.
In theory you should, however, say `gmake clean', `gmake all',
because configuration option changes could affect anything -- but in practice you are likely to know what's affected.
Go to the first, previous, next, last section, table of contents.