aboutsummaryrefslogtreecommitdiff
path: root/mesonbuild/modules/python.py
diff options
context:
space:
mode:
authorMarco Trevisan (Treviño) <mail@3v1n0.net>2021-05-07 20:20:29 +0200
committerJussi Pakkanen <jpakkane@gmail.com>2021-05-08 21:27:35 +0300
commit739e499554850d2cb8268bed219e8ba127051f76 (patch)
tree01f83e072029d70698b23b858ade37bfdbf1b950 /mesonbuild/modules/python.py
parent6033c0f0da764e9d81e35366a6ba81b8f6b984f7 (diff)
downloadmeson-739e499554850d2cb8268bed219e8ba127051f76.zip
meson-739e499554850d2cb8268bed219e8ba127051f76.tar.gz
meson-739e499554850d2cb8268bed219e8ba127051f76.tar.bz2
ninjabackend: Add pch includes as early as possible not to be overridden
When pch are used for a target meson will make the compiler to include the pre-compiled header. While this is useful, this needs to happen before any other header has been included, otherwise: 1) we won't take advantage of pch for anything else previously included 2) gcc will just fail as it won't even try to look for a pre-compiled header in this case [1] This case can happen quite a easily when a dependency provides an included header in its cflags. As per this, split _generate_single_compile() in two phases, one is responsible of initializing the compiler data, while the other is defining commands for the context. In this way, when pch can be used, we can insert the pch inclusion earlier than any other provided by the target. [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100462
Diffstat (limited to 'mesonbuild/modules/python.py')
0 files changed, 0 insertions, 0 deletions