aboutsummaryrefslogtreecommitdiff
path: root/mesonbuild/compilers/compilers.py
diff options
context:
space:
mode:
authorNicolas Schneider <nioncode+git@gmail.com>2019-01-01 23:31:41 +0100
committerNicolas Schneider <nioncode+git@gmail.com>2019-02-12 23:31:49 +0100
commitb1c3d150fe37a3f2c158ad7a90a2ae33ef95c218 (patch)
tree79b949f6f23cda9dcf6ccf815e31c75d1f98b680 /mesonbuild/compilers/compilers.py
parent82e4cb7731e59237746e480f9611700f1d4fda76 (diff)
downloadmeson-b1c3d150fe37a3f2c158ad7a90a2ae33ef95c218.zip
meson-b1c3d150fe37a3f2c158ad7a90a2ae33ef95c218.tar.gz
meson-b1c3d150fe37a3f2c158ad7a90a2ae33ef95c218.tar.bz2
vs: always consider run, install, and test targets out-of-date
Pre/PostBuildEvents do not run if no other build steps are out-of-date. For most run targets (including install and test) that have no other build steps, VS considers these to be always up-to-date after they have been built once. On the other hand, CustomBuild has clearly defined inputs and outputs that define whether the target is up-to-date or not. By using a nonexistent file as output of CustomBuild, it is always considered out-of-date. This aligns the VS behavior with ninja. `ninja install` unconditionally installs, `ninja test` always runs the tests, and a run target always gets executed, without any checks whether it is up-to-date or not.
Diffstat (limited to 'mesonbuild/compilers/compilers.py')
0 files changed, 0 insertions, 0 deletions