diff options
author | Dylan Baker <dylan@pnwbakers.com> | 2020-05-13 12:11:18 -0700 |
---|---|---|
committer | Dylan Baker <dylan@pnwbakers.com> | 2020-05-14 11:04:51 -0700 |
commit | a63e36f7b114d66f455936fa6621b30a3a54675f (patch) | |
tree | a9d141600baaa5d153810b1a1108976cb23f0221 /test cases/unit/36 exe_wrapper behaviour | |
parent | 4e9e35f3bd17a8f110ae1d3b40c8fbe04700120a (diff) | |
download | meson-a63e36f7b114d66f455936fa6621b30a3a54675f.zip meson-a63e36f7b114d66f455936fa6621b30a3a54675f.tar.gz meson-a63e36f7b114d66f455936fa6621b30a3a54675f.tar.bz2 |
interpreter: Rename has_exe_wrapper -> can_run_host_binaries
The implementation of this function has changed enough that the name
doesn't really reflect what it actually does. It basically returns true
unless you're cross compiling, need and exe_wrapper, and don't have one.
The original function remains but is marked as deprecated.
This makes one small change the meson source language, which is that it
defines that can_run_host_binaries will return true in build == host
compilation, which was the behavior that already existed. Previously
this was undefined in build == host compilation.
Diffstat (limited to 'test cases/unit/36 exe_wrapper behaviour')
-rw-r--r-- | test cases/unit/36 exe_wrapper behaviour/meson.build | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test cases/unit/36 exe_wrapper behaviour/meson.build b/test cases/unit/36 exe_wrapper behaviour/meson.build index 16a44d5..d0817ba 100644 --- a/test cases/unit/36 exe_wrapper behaviour/meson.build +++ b/test cases/unit/36 exe_wrapper behaviour/meson.build @@ -1,7 +1,7 @@ project('exe wrapper behaviour', 'c') assert(meson.is_cross_build(), 'not setup as cross build') -assert(meson.has_exe_wrapper(), 'exe wrapper not defined?') +assert(meson.has_exe_wrapper(), 'exe wrapper not defined?') # intentionally not changed to can_run_host_binaries, exe = executable('prog', 'prog.c') |