From 4ae405e914578127efbe0eedcfec6d81780bee98 Mon Sep 17 00:00:00 2001 From: Arch Librarian Date: Mon, 20 Sep 2004 16:57:04 +0000 Subject: JoeyH's dpkg::preconfig not working. Author: jgg Date: 2001-03-05 21:09:12 GMT JoeyH's dpkg::preconfig not working. --- README.make | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) (limited to 'README.make') diff --git a/README.make b/README.make index 7fd6ae5e8..c043f10f6 100644 --- a/README.make +++ b/README.make @@ -26,12 +26,12 @@ and configure substitutions across build makefiles is not used at all. Furthermore, the make system runs with a current directory equal to the source directory irregardless of the destination directory. This means -#include "" and #include <> work as epected and more importantly +#include "" and #include <> work as expected and more importantly running 'make' in the source directory will work as expected. The -environment variable or make parameter 'BUILD' set the build directory. +environment variable or make parameter 'BUILD' sets the build directory. It may be an absolute path or a path relative to the top level directory. -By default build/ will be used with a fall back to ./ This means -you can get all the advantages of a build directory without having to +By default build-arch/ then build/ will be used with a fall back to ./ This +means you can get all the advantages of a build directory without having to cd into it to edit your source code! The make system also performs dependency generation on the fly as the @@ -49,10 +49,8 @@ the source directory but is logically divided in the following manner examples/ include/ apt-pkg/ - deity/ obj/ apt-pkg/ - deity/ cmndline/ [...] Only .o and .d files are placed in the obj/ subdirectory. The final compiled -- cgit v1.2.3