commit | 9694f9fefeee6ac7c729c3a520c43902e6fb76f1 | [log] [tgz] |
---|---|---|
author | Mis012 <Michael.Srba@seznam.cz> | Thu Feb 15 20:21:56 2024 +0100 |
committer | Jussi Pakkanen <jpakkane@gmail.com> | Mon Jun 10 01:48:53 2024 +0300 |
tree | 2d3b3a20b1fc1c2b0bceeaa694e8e2d6f4aee4ee | |
parent | 374fa7f0da278d46a4c3adb587f4b43089f5d7db [diff] |
java: use single javac invocation per jar Instead of invoking javac for every .java file, pass all of the sources for a jar target to a single javac invocation. This massively improves first compilation time and doesn't meaningfully affect incremental builds (it can even be faster in some cases). The old approach also had issues where files would not always get recompiled even though they should, necessitating a clean rebuild in order to see changes reflected in the build output. Multiple invocations seem to only make sense if: - issues with files not getting flagged for rebuild are investigated and fixed - something like the javaserver buildtool from openjdk sources is used instead of directly spawning javac processes - the amount of java files per jar is so large that it is faster to compile several files one by one than to compile all the files at once (batching may still make sense to get a reasonable balance)
Latest Meson version supporting previous Python versions:
Meson is available on PyPi, so it can be installed with pip3 install meson
. The exact command to type to install with pip
can vary between systems, be sure to use the Python 3 version of pip
.
If you wish you can install it locally with the standard Python command:
python3 -m pip install meson
For builds using Ninja, Ninja can be downloaded directly from Ninja GitHub release page or via PyPi
python3 -m pip install ninja
More on Installing Meson build can be found at the getting meson page.
Meson can be run as a Python zip app. To generate the executable run the following command:
./packaging/create_zipapp.py --outfile meson.pyz --interpreter '/usr/bin/env python3' <source checkout>
Meson requires that you have a source directory and a build directory and that these two are different. In your source root must exist a file called meson.build
. To generate the build system run this command:
meson setup <source directory> <build directory>
Depending on how you obtained Meson the command might also be called meson.py
instead of plain meson
. In the rest of this document we are going to use the latter form.
You can omit either of the two directories, and Meson will substitute the current directory and autodetect what you mean. This allows you to do things like this:
cd <source root> meson setup builddir
To compile, cd into your build directory and type ninja
. To run unit tests, type ninja test
.
More on running Meson build system commands can be found at the running meson page or by typing meson --help
.
We love code contributions. See the contribution page on the website for details.
The channel to use is #mesonbuild
either via Matrix (web interface) or OFTC IRC.
More information about the Meson build system can be found at the project's home page.
Meson is a registered trademark of Jussi Pakkanen.