diff options
author | Nirbheek Chauhan <nirbheek.chauhan@gmail.com> | 2016-07-19 02:30:17 +0530 |
---|---|---|
committer | Jussi Pakkanen <jpakkane@gmail.com> | 2016-07-19 00:00:17 +0300 |
commit | 69d9c2228d718a627fdb3f8504cbc4cdff0b1f4c (patch) | |
tree | c8cf3665adca14df99e5fcada7ac1a4366fcb542 /run_cross_test.py | |
parent | 129ce6800c7ebcb0a9f3c6233fc8deb071b66e59 (diff) | |
download | meson-69d9c2228d718a627fdb3f8504cbc4cdff0b1f4c.zip meson-69d9c2228d718a627fdb3f8504cbc4cdff0b1f4c.tar.gz meson-69d9c2228d718a627fdb3f8504cbc4cdff0b1f4c.tar.bz2 |
vs: Fix Meson invocation while doing regen (#646)
The Meson script is not always in $scriptdir/../../ -- for instance if
installed with pip on Windows, the scriptdir is in:
C:/Python35/Lib/site-packages/meson-0.33.0.dev1-py3.5.egg/mesonbuild/scripts
and the meson.py script is in:
C:/Python35/Scripts
So, let's save the path available as Environment().meson_script_file
into the coredata.dat private file and use that to invoke Meson when
doing regen.
Also, let's fetch the backend that was used from the coredata too
instead of hard-coding vs2010.
Both these were causing a hard failure while doing regen with msbuild or
visual studio.
Diffstat (limited to 'run_cross_test.py')
0 files changed, 0 insertions, 0 deletions