From 4250f552a6c78f5547d45c77b46ea11c5e8e394d Mon Sep 17 00:00:00 2001 From: Colin Watson Date: Thu, 26 Jun 2014 14:20:17 +0100 Subject: [PATCH] * docs/grub-dev.texi (Finding your way around): The build system no longer uses AutoGen directly. --- ChangeLog | 5 +++++ docs/grub-dev.texi | 6 +++--- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index be322d48c..5109c5a61 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2014-06-26 Colin Watson + + * docs/grub-dev.texi (Finding your way around): The build system no + longer uses AutoGen directly. + 2014-06-21 Роман Пехов * grub-core/commands/loadenv.c (check_blocklists): Fix overlap check. diff --git a/docs/grub-dev.texi b/docs/grub-dev.texi index 7c6244cdb..a9f4de631 100644 --- a/docs/grub-dev.texi +++ b/docs/grub-dev.texi @@ -228,12 +228,12 @@ The opening @samp{/*} and closing @samp{*/} should be placed together on a line Here is a brief map of the GRUB code base. GRUB uses Autoconf and Automake, with most of the Automake input generated -by AutoGen. The top-level build rules are in @file{configure.ac}, +by a Python script. The top-level build rules are in @file{configure.ac}, @file{grub-core/Makefile.core.def}, and @file{Makefile.util.def}. Each block in a @file{*.def} file represents a build target, and specifies the source files used to build it on various platforms. The @file{*.def} files -are processed into AutoGen input by @file{gentpl.py} (which you only need to -look at if you are extending the build system). If you are adding a new +are processed into Automake input by @file{gentpl.py} (which you only need +to look at if you are extending the build system). If you are adding a new module which follows an existing pattern, such as a new command or a new filesystem implementation, it is usually easiest to grep @file{grub-core/Makefile.core.def} and @file{Makefile.util.def} for an