vbatts/grub
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

* docs/grub-dev.texi (Finding your way around): The build system no

Browse source 
longer uses AutoGen directly.
This commit is contained in:
Colin Watson 2014-06-26 14:20:17 +01:00
parent 1f6af2a9f8
commit 4250f552a6
2 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
ChangeLog
View file

@ -1,3 +1,8 @@
2014-06-26 Colin Watson <cjwatson@ubuntu.com>
* docs/grub-dev.texi (Finding your way around): The build system no
longer uses AutoGen directly.
2014-06-21 Роман Пехов <roman_pekhov> 2014-06-21 Роман Пехов <roman_pekhov>
* grub-core/commands/loadenv.c (check_blocklists): Fix overlap check. * grub-core/commands/loadenv.c (check_blocklists): Fix overlap check.

6
docs/grub-dev.texi
View file

@ -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. Here is a brief map of the GRUB code base.
GRUB uses Autoconf and Automake, with most of the Automake input generated 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 @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 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 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 are processed into Automake input by @file{gentpl.py} (which you only need
look at if you are extending the build system). If you are adding a new 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 module which follows an existing pattern, such as a new command or a new
filesystem implementation, it is usually easiest to grep filesystem implementation, it is usually easiest to grep
@file{grub-core/Makefile.core.def} and @file{Makefile.util.def} for an @file{grub-core/Makefile.core.def} and @file{Makefile.util.def} for an