From 3d7ec2f804af7c9c757782ff72d98591a873b533 Mon Sep 17 00:00:00 2001 From: "jochen@chromium.org" Date: Wed, 4 Jun 2014 11:05:46 +0000 Subject: Always process landmines, even if GYP_CHROMIUM_NO_ACTION is set R=machenbach@chromium.org BUG=none Review URL: https://codereview.chromium.org/314933004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274762 0039d316-1c4b-4281-b951-d872f2087c98 --- build/gyp_chromium | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'build/gyp_chromium') diff --git a/build/gyp_chromium b/build/gyp_chromium index 26028dc..48c7389 100755 --- a/build/gyp_chromium +++ b/build/gyp_chromium @@ -190,6 +190,10 @@ if __name__ == '__main__': args = sys.argv[1:] if int(os.environ.get('GYP_CHROMIUM_NO_ACTION', 0)): + # Check for landmines (reasons to clobber the build) in any case. + print 'Running build/landmines.py...' + subprocess.check_call( + [sys.executable, os.path.join(script_dir, 'landmines.py')]) print 'Skipping gyp_chromium due to GYP_CHROMIUM_NO_ACTION env var.' sys.exit(0) -- cgit v1.1