Dropping remaining scons references.
The old hammer entry points and use of scons for chromium is long gone. Dropping it. BUG=None TEST=None R=dpranke@chromium.org Review-Url: https://codereview.chromium.org/2016053004 git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@300667 0039d316-1c4b-4281-b951-d872f2087c98changes/30/350330/1
parent
0305afaf4a
commit
cfbab8fc1f
@ -1,28 +0,0 @@
|
||||
#!/bin/sh
|
||||
#
|
||||
# Copyright (c) 2006-2008 The Chromium Authors. All rights reserved.
|
||||
# Use of this source code is governed by a BSD-style license that can be
|
||||
# found in the LICENSE file.
|
||||
|
||||
# A script to invoke scons in gyp generated projects.
|
||||
|
||||
# Find the 'src' directory by looking for the site_scons directory.
|
||||
# This method allows trees that don't use the name src to use this script.
|
||||
# Explicitly skip site_scons directories that are from the 'software
|
||||
# construction toolkit', since these are not gyp compatible.
|
||||
SRC_DIR=`pwd`
|
||||
while [ ! -d "${SRC_DIR}/site_scons" ] || \
|
||||
[ -e "${SRC_DIR}/site_scons/site_tools/component_setup.py" ]; do
|
||||
PARENT_DIR="$(dirname "${SRC_DIR}")"
|
||||
if [ "${SRC_DIR}" = "${PARENT_DIR}" ]; then
|
||||
echo "ERROR: hammer must be run in a directory with site_scons under" >&2
|
||||
echo " the root of the project tree." >&2
|
||||
exit 1
|
||||
fi
|
||||
SRC_DIR="${PARENT_DIR}"
|
||||
done
|
||||
|
||||
SCONS="${SRC_DIR}/third_party/scons/scons.py"
|
||||
SITE_SCONS="${SRC_DIR}/site_scons"
|
||||
|
||||
exec python "${SCONS}" "--site-dir=${SITE_SCONS}" "$@"
|
@ -1,23 +0,0 @@
|
||||
@echo off
|
||||
|
||||
|
||||
@rem We're in a submodule directory, look relative to the parent.
|
||||
call python "%cd%\..\third_party\scons\scons.py" "--site-dir=..\site_scons" %*
|
||||
goto omega
|
||||
|
||||
:srcdir
|
||||
call python "%cd%\third_party\scons\scons.py" --site-dir=site_scons %*
|
||||
goto omega
|
||||
|
||||
@rem Per the following page:
|
||||
@rem http://code-bear.com/bearlog/2007/06/01/getting-the-exit-code-from-a-batch-file-that-is-run-from-a-python-program/
|
||||
@rem Just calling "exit /b" passes back an exit code, but in a way
|
||||
@rem that does NOT get picked up correctly when executing the .bat
|
||||
@rem file from the Python subprocess module. Using "call" as the
|
||||
@rem last command in the .bat file makes it work as expected.
|
||||
|
||||
:returncode
|
||||
exit /b %ERRORLEVEL%
|
||||
|
||||
:omega
|
||||
call :returncode %ERRORLEVEL%
|
Loading…
Reference in New Issue