|
14.2 Fine-grained control of install
The second most common way (30) to configure a package is to set
To this end, Automake provides finer control to the user than a simple
In the above scenario, installing the architecture-independent files
more than once is just a waste of time. Our hypothetical administrator
can install those pieces exactly once, with
Nonstandard directories specified in `Makefile.am' are also
separated along `data' and `exec' lines, giving the user
complete control over installation. If, and only if, the directory
variable name contains the string `exec', then items ending up in
that directory will be installed by At some sites, the paths referred to by software at runtime differ from those used to actually install the software. For instance, suppose `/usr/local' is mounted read-only throughout the network. On the server, where new packages are built, the file system is available read-write as `/w/usr/local' -- a directory which is not mounted anywhere else. In this situation the sysadmin can configure and build using the runtime values, but use the `DESTDIR' trick to temporarily change the paths at install time:
Note that `DESTDIR' operates as a prefix only. Sometimes this isn't enough. In this situation you can explicitly override each directory variable:
Here is a full example (31) showing how you can unpack, configure, and build a typical GNU program on multiple machines at the same time:
In one window:
And in another window:
In this example we install everything on the `sunos' machine, but
we only install the platform-dependent files on the `linux'
machine. We use a different
|