aboutsummaryrefslogtreecommitdiff
path: root/mesonbuild/mintro.py
diff options
context:
space:
mode:
authorChristoph Reiter <reiter.christoph@gmail.com>2019-05-25 19:01:44 +0200
committerJussi Pakkanen <jpakkane@gmail.com>2019-05-28 20:25:37 +0300
commit20eb948b974a96b3933d42db524fd584cb60c8b7 (patch)
treecb2f852c349b661b827e803a661d45e74a40368a /mesonbuild/mintro.py
parent949187868196edc4fa3ba21b033f8a08a2b391d6 (diff)
downloadmeson-20eb948b974a96b3933d42db524fd584cb60c8b7.zip
meson-20eb948b974a96b3933d42db524fd584cb60c8b7.tar.gz
meson-20eb948b974a96b3933d42db524fd584cb60c8b7.tar.bz2
gnome: make sure the target build directory is passed first for linking
determine_rpath_dirs() can return paths to external dependencies not in the build dir and passing them first as a link path leads to g-ir-scanner for example linking against the already installed library instead of the just built one. This was reported in g-i: https://gitlab.gnome.org/GNOME/gobject-introspection/issues/272 and comes up quite often when a library adds some new symbols which aren't present in the system library, which then makes linking fail. The first place where the order is changed is _scan_gir_targets(), which looks like an unintentional change in the refactoring in 8377ea45aa61efbe8e1a75b74 The second place in _get_link_args() has always been that way and only the rpath order is changed, but it looks to me as if the same rules should apply here too.
Diffstat (limited to 'mesonbuild/mintro.py')
0 files changed, 0 insertions, 0 deletions