armhf (hardware float) is the ubuntu default these
days so should be used over armel in most cases.
Also, the chromium ARM/linux test hardware is
running armhf.
This CL does not change the default or remove armel
support. That is left for a future CL.
BUG=308256
Review URL: https://codereview.chromium.org/27197011
git-svn-id: http://src.chromium.org/svn/trunk/src/build@231487 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This is a lightweight check to alert developers when their build
dependencies are out-of-date, and hopefully avoid confusing compile
errors. It takes < 1 second to run, so can be checked whenever sources
are synced, and might even by worth including as a default step in
gyp_chromium or DEPS hooks.
By definition, this is not a complete check, and in particular, will not
detect version updates of installed dependencies. It's mostly intended
to detect when entirely new dependencies have been added.
R=markus@chromium.org, sky@chromium.org
Review URL: https://codereview.chromium.org/40603004
git-svn-id: http://src.chromium.org/svn/trunk/src/build@231030 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The test for libudev1/libudev0 fails when an sdk has installed
a dependency on libudev1, which will go away on recompile, on
a system with only libudev0. The dependency created an empty
virtual package that passes the "show" test, but cannot be installed.
BUG=243398
TEST=local
Review URL: https://chromiumcodereview.appspot.com/15911004
git-svn-id: http://src.chromium.org/svn/trunk/src/build@202021 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This needs a little bit of explanation. Normally, we would want to restructure
the code to have separate variables for "--lib32" and for the result of the
"yes_no" question. But that requires more global changes.
Instead, in this case, we want to very clearly document that we added an
early "if" statement to break out. And this is intended to be a temporary
measure until the entire feature is fully removed.
So, I instead opted for resetting the "do_inst_lib32" variable -- and a lengthy
comment explaining this decision.
BUG=233047
TEST=run with --lib32 and verify that entering "N" aborts the installation.
Review URL: https://chromiumcodereview.appspot.com/14166013
git-svn-id: http://src.chromium.org/svn/trunk/src/build@195950 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
install-build-deps.sh runs "sudo /path/to/src/build/linux/install-chromeos-fonts.py".
If the repo is on a filer, sudo fails because root is not allowed to access files on
a filer. However, installing a Repo on a Filer is not recommended.
Solution:
install-build-deps.sh attempts to detect that the Repo is not on a Filer and
in that case prints a warning with instructions.
Note: install-build-deps.sh exits immediately on failure because it uses "bash -e".
BUG=225543
R=derat@chromium.org
TEST=manual
Review URL: https://chromiumcodereview.appspot.com/13532003
git-svn-id: http://src.chromium.org/svn/trunk/src/build@192485 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Added call to a new script in:
build/install-build-deps.sh
to download and install the ChromeOS default font
(Noto Sans UI). The installation is in:
/usr/local/share/fonts.
ChromeOS on Linux will use the font if present.
The installation creates (or recreates) a subdir:
"chromeos". In it it creates a .stamp file which is used
to avoid re-installation if it is already up to date.
It also creates a README file.
BUG=148945
TEST=manual;
One way to test is to instrument the file:
src/ui/gfx/platform_font_pango.cc
to log default_font_->GetFontName(); in ctor
PlatformFontPango::PlatformFontPango()
Expect:
W/out font installation: DejaVu Sans
With font installation: Noto Sans UI
Review URL: https://chromiumcodereview.appspot.com/12313039
git-svn-id: http://src.chromium.org/svn/trunk/src/build@184006 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Add an option --unsupported to install-build-deps.sh which allows the
installation to be attempted on a system we don't support. Omit
mentioning this in the error, in the hope that anyone who can deal with
the fallout from this will find it in the script. Also, add GCEL
(Ubuntu-derived image used by Compute Engine) to the list of supported
systems.
BUG=
Review URL: https://codereview.chromium.org/11863012
git-svn-id: http://src.chromium.org/svn/trunk/src/build@176982 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
install-arm-sysroot.py is now seperated out from
install-build-deps.sh so that it can be invoked
independently by the gclient hooks.
This addresses a couple of different issues with
configuring the arm buildbots. Firstly it means
that they will always have an up-to-date arm
sysroot installed. Secondly, it means the script
is always run as the user (and not as root) which
mean the expanded files that the correct ownership.
BUG=
Review URL: https://chromiumcodereview.appspot.com/11468014
git-svn-id: http://src.chromium.org/svn/trunk/src/build@171990 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Native client toolchain still need some extra 32 bit libraries belong to
packages libc6-i386 and lib32gcc1. Instead of adding all 32-bit libraries,
adding above two packages in common (64-bit and 32-bit) makes more sense.
TEST=build on 64-bit linux
BUG=138234
Review URL: https://chromiumcodereview.appspot.com/10810035
git-svn-id: http://src.chromium.org/svn/trunk/src/build@148356 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
mcgrathr@chromium.org
sbc@chromium.org
alextaran@chromium.org
erg@chromium.org
derat@chromium.org
earthdok@chromium.org
pschmidt@google.com
jln@chromium.org
mmoss@chromium.org
torne@chromium.org
petermayo@chromium.org
thestig@chromium.org
akalin@chromium.org
plundblad@chromium.org
solb@chromium.org
halton.huo@intel.com
Vanuan@gmail.com
markus@chromium.org
sschmitz@chromium.org
victorhsieh@chromium.org
xians@chromium.org
bevc@chromium.org
pph34r@gmail.com
sergeyu@chromium.org
phajdan.jr@chromium.org
tfarina@chromium.org
toyoshim@chromium.org
jochen@chromium.org
cmp@chromium.org
bryeung@chromium.org