Difference between revisions of "Build Tools"
(→Autotools: Rewrite for clarity.) |
(→Autotools (deprecated): dropped by gnucash) |
||
| (24 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | ||
| + | {| class="wikitable" style="margin: auto;" | ||
| + | ! scope="row"|Languages | ||
| + | | [[de/{{PAGENAME:Gnucash}}|Deutsch]] | ||
| + | | [[He/{{PAGENAME:כלי_בניה}}|עִברִית]] | ||
| + | |} | ||
The GnuCash project uses several different tools to build the program, the docs, and OS specific packages. | The GnuCash project uses several different tools to build the program, the docs, and OS specific packages. | ||
| Line 6: | Line 11: | ||
=== Make === | === Make === | ||
| − | [https://en.wikipedia.org/wiki/Make_(software) Make] is a ''build automation tool'' that builds | + | [https://en.wikipedia.org/wiki/Make_(software) Make] is a ''build automation tool'' that builds targets from source by interpreting recipe files called ''Makefiles'' which specify how to transform the source file(s) into the target file(s). Many "Integrated Development Environments" or "IDEs" use <code>make</code> (or its Microsoft cousin <code>nmake</code>) to perform the build. Makefiles can be written by hand (as is the case for '''gnucash-htdocs.git''') or generated by [[#Autotools|Autotools]] or [[#CMake|CMake]]. Make can be invoked recursively to build complex programs and use file timestamps to only recompile files and libraries where a dependency has been changed. Makefiles ususally specify a number of targets of the build which may be supplied as arguments when make is called to perform specific actions to produce specific outputs. |
| − | |||
| − | |||
=== Ninja === | === Ninja === | ||
[https://en.wikipedia.org/wiki/Ninja_(build_system) Ninja] is a small build system with a focus on speed. It is designed to have its input files generated by a higher-level build system, and it is designed to run builds as fast as possible. | [https://en.wikipedia.org/wiki/Ninja_(build_system) Ninja] is a small build system with a focus on speed. It is designed to have its input files generated by a higher-level build system, and it is designed to run builds as fast as possible. | ||
;Note: The commands change then from <code>make [target]</code> to <code>ninja [target]</code>. | ;Note: The commands change then from <code>make [target]</code> to <code>ninja [target]</code>. | ||
| + | ;Note: Some Linux distributions name the command <code>ninja-build</code> to distinguish it from another program called <code>ninja</code>. | ||
| + | A comparison of CMake with the make utility is available [https://ninja-build.org/manual.html#_comparison_to_make here] | ||
| − | + | [[#CMake|CMake]] is commonly used to configure <code>ninja</code> build files: To do so pass <code>-G Ninja</code> among the <code>cmake</code> arguments. | |
== Tool Chains == | == Tool Chains == | ||
| − | In addition, GnuCash uses different ''tool chains'' to control the basic tools mentioned above. The program makes use of the '''CMake''' tool chain, while the documentation uses the '''Autotools''' tool chain. The website is compiled directly using [[#Make|Make]]. | + | In addition, GnuCash uses different ''tool chains'' to control the basic tools mentioned above. The program makes use of the '''CMake''' as the base of its tool chain, while the user documentation uses the '''Autotools''' as the base of the tool chain. The website is compiled directly using [[#Make|Make]]. The API documentation is created from the source code using [[#Make|Make]] or [[#Ninja|Ninja]], depending on how the source code build system is configured. |
=== CMake === | === CMake === | ||
| − | To | + | To set up or configure the '''program''' build system, we use [https://en.wikipedia.org/wiki/CMake CMake]. It should also be used for the '''Gnucash-docs'''. |
| + | |||
| + | It is a cross-platform free and open-source software application for managing the build process of software using a compiler-independent method. It supports directory hierarchies and applications that depend on multiple libraries. It is used in conjunction with native build environments such as make, Apple's Xcode, and Microsoft Visual Studio. It has minimal dependencies, requiring only a C++ compiler on its own build system. At present, CMake is primarily used to configure the build system by creating the input files for either the '''make''' or the '''ninja''' build programs which compile and link the program and its libraries. These utilities also control installation of the program and libraries. | ||
| + | See [[CMake#GnuCash Configuration Variables]]. | ||
| − | === Autotools === | + | === Autotools (no longer used by us, but several of our dependencies) === |
| − | + | We used to rely on the [https://en.wikipedia.org/wiki/GNU_Build_System GNU Build System] to set up or configure the '''Gnucash-docs''' build system. This is also often referred to as "autotools". We dropped it in Gnucash 4.7! | |
| + | |||
| + | It's a complex and capable system for configuring and building a wide range of projects on a wide range of platforms. [https://autotools.io/index.html The Autotools Mythbuster] provides an excellent tutorial and reference for those wishing to learn about creating and building projects using the system. | ||
For those who simply need to build the documentation from source, the following three commands will suffice: | For those who simply need to build the documentation from source, the following three commands will suffice: | ||
#<code>autogen.sh</code>: Checks that all required parts of the build system are installed, then builds the <code>configure</code> program from its source, <code>configure.ac</code> and the intermediate Makefiles <code>Makefile.in</code> from their source <code>Makefile.am</code>. You'll run <code>autogen.sh</code> after you first clone <code>gnucash-docs.git</code>, any time you edit a <code>Makefile.am</code> or <code>configure.ac</code>, and any time you pull commits with changes to those files. Since it does no harm to run it unnecessarily we recommend that you run it after any <code>git pull</code>. | #<code>autogen.sh</code>: Checks that all required parts of the build system are installed, then builds the <code>configure</code> program from its source, <code>configure.ac</code> and the intermediate Makefiles <code>Makefile.in</code> from their source <code>Makefile.am</code>. You'll run <code>autogen.sh</code> after you first clone <code>gnucash-docs.git</code>, any time you edit a <code>Makefile.am</code> or <code>configure.ac</code>, and any time you pull commits with changes to those files. Since it does no harm to run it unnecessarily we recommend that you run it after any <code>git pull</code>. | ||
| + | #(not required, but suggested)<Syntaxhighlight lang="sh"> | ||
| + | mkdir .build | ||
| + | cd .build</Syntaxhighlight> | ||
| + | #;Note: <tt>configure</tt> and <tt>make</tt> commands are run from this ${BUILDDIR} while sources are edited in the parental ${SOURCEDIR}. | ||
#<code>configure</code>: This shell script, generated by <code>autogen.sh</code> as described above, examines your system and its arguments to convert the intermediate <code>Makefile.in<code> to <code>Makefile</code> that the <code>make</code> command will use to actually generate the documentation product files. One can get a listing of the arguments and environment variables that any particular <code>configure</code> understands by running <code>configure --help</code>. | #<code>configure</code>: This shell script, generated by <code>autogen.sh</code> as described above, examines your system and its arguments to convert the intermediate <code>Makefile.in<code> to <code>Makefile</code> that the <code>make</code> command will use to actually generate the documentation product files. One can get a listing of the arguments and environment variables that any particular <code>configure</code> understands by running <code>configure --help</code>. | ||
| − | #<code>make</code>: Using <code>Makefile</code> as a template, <code>make</code> runs the various programs and scripts needed to perform the build. Its arguments are the targets to be built; there are two special targets, <code>check</code> runs tests to ensure that the project has been built correctly and <code>install</code> moves the build products to the locations from which they may be used. | + | #<code>make</code>: Using <code>Makefile</code> as a template, <code>make</code> runs the various programs and scripts needed to perform the build. Its arguments are the targets to be built; there are two special targets, <code>make check</code> runs tests to ensure that the project has been built correctly and <code>make install</code> moves the build products to the locations from which they may be used. |
| − | [[Category:Development]] | + | |
| + | '''Return to: | ||
| + | |||
| + | [[Building |Building GnuCash]] | ||
| + | |||
| + | [[Category:Development]] [[Category:Building]] [[Category:Tools]] | ||
Latest revision as of 19:38, 20 October 2021
| Languages | Deutsch | עִברִית |
|---|
The GnuCash project uses several different tools to build the program, the docs, and OS specific packages.
Contents
Basic Tools
These control the build process at a low level.
Make
Make is a build automation tool that builds targets from source by interpreting recipe files called Makefiles which specify how to transform the source file(s) into the target file(s). Many "Integrated Development Environments" or "IDEs" use make (or its Microsoft cousin nmake) to perform the build. Makefiles can be written by hand (as is the case for gnucash-htdocs.git) or generated by Autotools or CMake. Make can be invoked recursively to build complex programs and use file timestamps to only recompile files and libraries where a dependency has been changed. Makefiles ususally specify a number of targets of the build which may be supplied as arguments when make is called to perform specific actions to produce specific outputs.
Ninja
Ninja is a small build system with a focus on speed. It is designed to have its input files generated by a higher-level build system, and it is designed to run builds as fast as possible.
- Note
- The commands change then from
make [target]toninja [target]. - Note
- Some Linux distributions name the command
ninja-buildto distinguish it from another program calledninja.
A comparison of CMake with the make utility is available here
CMake is commonly used to configure ninja build files: To do so pass -G Ninja among the cmake arguments.
Tool Chains
In addition, GnuCash uses different tool chains to control the basic tools mentioned above. The program makes use of the CMake as the base of its tool chain, while the user documentation uses the Autotools as the base of the tool chain. The website is compiled directly using Make. The API documentation is created from the source code using Make or Ninja, depending on how the source code build system is configured.
CMake
To set up or configure the program build system, we use CMake. It should also be used for the Gnucash-docs.
It is a cross-platform free and open-source software application for managing the build process of software using a compiler-independent method. It supports directory hierarchies and applications that depend on multiple libraries. It is used in conjunction with native build environments such as make, Apple's Xcode, and Microsoft Visual Studio. It has minimal dependencies, requiring only a C++ compiler on its own build system. At present, CMake is primarily used to configure the build system by creating the input files for either the make or the ninja build programs which compile and link the program and its libraries. These utilities also control installation of the program and libraries. See CMake#GnuCash Configuration Variables.
Autotools (no longer used by us, but several of our dependencies)
We used to rely on the GNU Build System to set up or configure the Gnucash-docs build system. This is also often referred to as "autotools". We dropped it in Gnucash 4.7!
It's a complex and capable system for configuring and building a wide range of projects on a wide range of platforms. The Autotools Mythbuster provides an excellent tutorial and reference for those wishing to learn about creating and building projects using the system.
For those who simply need to build the documentation from source, the following three commands will suffice:
autogen.sh: Checks that all required parts of the build system are installed, then builds theconfigureprogram from its source,configure.acand the intermediate MakefilesMakefile.infrom their sourceMakefile.am. You'll runautogen.shafter you first clonegnucash-docs.git, any time you edit aMakefile.amorconfigure.ac, and any time you pull commits with changes to those files. Since it does no harm to run it unnecessarily we recommend that you run it after anygit pull.- (not required, but suggested)
mkdir .build cd .build- Note
- configure and make commands are run from this ${BUILDDIR} while sources are edited in the parental ${SOURCEDIR}.
configure: This shell script, generated byautogen.shas described above, examines your system and its arguments to convert the intermediateMakefile.in<code> to <code>Makefilethat themakecommand will use to actually generate the documentation product files. One can get a listing of the arguments and environment variables that any particularconfigureunderstands by runningconfigure --help.make: UsingMakefileas a template,makeruns the various programs and scripts needed to perform the build. Its arguments are the targets to be built; there are two special targets,make checkruns tests to ensure that the project has been built correctly andmake installmoves the build products to the locations from which they may be used.
Return to:
