Re: Which targets are mandatory in debian/rules?

[Jules Bean <jmlb2@hermes.cam.ac.uk>]

On Sun, 14 Feb 1999, Hamish Moffatt wrote:

> On Sun, Feb 14, 1999 at 12:12:26PM +0000, Jules Bean wrote:
> > And conversely, of course there is at least one technical reason to prefer
> > doing all the build in the 'build' target - the 'binary' target may be run
> > as root (more likely fakeroot, I admit, but possibly actual root).
> > 
> > It seems to me that policy should be changed, here.
> 
> This may bmean the build target ends up doing part of the binary
> target's work though. For example I have the packages sattrack 
> and sattrack-x11, which are built from the same source. I hacked
> the Makefile so I can enable or disable the X support from debian/rules,
> but the whole thing needs to be cleaned out and rebuilt for whichever
> version. Hence I have a dummy `build' target. It already does weird stuff
> during building with objects in other directories...

Any package which uses the GNU toolchain can be build in multiple
directories like this:

mkdir debian/build-no-x; cd debian/build-no-x; ../../configure --disable-x
make

mkdir debian/build-x; cd debian/build-x; ../../configure --enable-x
make

(or something like that, anyhow)

This is a preferable technique where practicable (admittedly, it's heavy
on the disk space).

Jules

/----------------+-------------------------------+---------------------\
|  Jelibean aka  | jules@jellybean.co.uk         |  6 Evelyn Rd	       |
|  Jules aka     | jules@debian.org              |  Richmond, Surrey   |
|  Julian Bean   | jmlb2@hermes.cam.ac.uk        |  TW9 2TF *UK*       |
+----------------+-------------------------------+---------------------+
|  War doesn't demonstrate who's right... just who's left.             |
|  When privacy is outlawed... only the outlaws have privacy.          |
\----------------------------------------------------------------------/