Now that we have more and more proper grd dependencies in place,
this script may just do more harm than good by causing spurious rebuilds.
Additionally, it horked the build today.
TEST=none
BUG=17706
Review URL: http://codereview.chromium.org/1019007
git-svn-id: http://src.chromium.org/svn/trunk/src/build@41947 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
- I put the dev library in the runtime section,
- I missed the runtime library (?\127libdbus-glib-1-2) altogether
- These issues were masked as apt-get couldn't resolve lib32readline-dev
replacing it with lib32readline6-dev appears to solve this.
BUG=http://crbug.com/37199
TEST=none
Review URL: http://codereview.chromium.org/811007
git-svn-id: http://src.chromium.org/svn/trunk/src/build@41276 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This lets us use portage-based cross-compiled sysroots, that force the prefix to be an absolute path within the portage chroot.
In particular that lets us build the ARM sysroot using the Chrome OS build system.
Ubuntu-based sysroots already have prefix=/usr, so this is a no-op in that case.
Review URL: http://codereview.chromium.org/669139
git-svn-id: http://src.chromium.org/svn/trunk/src/build@40712 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The scons generator currently does not correctly handle the case in which you
have a target with no sources (for instance all the mock targets used for the
bots). So far this has not been an issue because these mock targets were only
used for Windows and Mac. jiesun's recent addition of a chromeos_builder target
caused this issue to manifest itself.
BUG=None
TEST=None
TBR=jiesuN
Review URL: http://codereview.chromium.org/661249
git-svn-id: http://src.chromium.org/svn/trunk/src/build@40229 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
For ffmpeg, I copied the "arm" configs (which include neon) into "arm-neon" configs, and changed HAVE_NEON=1 to 0 in the existing ones. Also, I removed the explicit cflags in ffmpeg.gyp since they are already set in common.gypi
Review URL: http://codereview.chromium.org/660067
git-svn-id: http://src.chromium.org/svn/trunk/src/build@40163 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
When compiling with the new portage build system for Chromium OS,
paths passed in for includes, libraries, etc., are already properly
prefixed with the sysroot and do not need to be again prefixed with
the sysroot.
Review URL: http://codereview.chromium.org/652067
git-svn-id: http://src.chromium.org/svn/trunk/src/build@39655 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
but currently only on the Mac.
These relationships should be errors on all platforms, but some currently
exist on non-Mac platforms. See http://crbug.com/35878. Because the Mac is
the only platform where a circular dependency between .gyp files is known to
cause tangible problems, the portions of Chromium's .gyp files that are used
by Macs have been fixed to remove these relationships, and the check is left
enabled on the Mac to ensure that no new ones are created.
BUG=35308
TEST=none
Review URL: http://codereview.chromium.org/600151
git-svn-id: http://src.chromium.org/svn/trunk/src/build@39128 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
test_shell.gyp. This allows the removal of webkit.gyp:pull_in_test_shell,
eliminating the circular relationship between webkit.gyp and test_shell.gyp.
The expected semantics of building all of test_shell during a webkit.gyp:All
build is performed are retained.
This change depends on GYP r781 (in Chromium at r38526) for GYP suffix
operator path section treatment. It also depends on Chromium r38519 and
r38658 for common.gypi treatment of chromium_code.
BUG=33186
TEST=Xcode no longer holds stale project files in memory
Review URL: http://codereview.chromium.org/602006
git-svn-id: http://src.chromium.org/svn/trunk/src/build@38664 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
file scope.
This extends r38519, which was incomplete.
To resolve bug 33186, I am trying to turn test_shell.gyp into test_shell.gypi,
and have webkit.gyp include it. webkit.gyp is not chromium_code, but the
targets in test_shell.gypi are.
BUG=33186
TEST=builds still work, -Werror and friends are still applied (or not)
correctly
Review URL: http://codereview.chromium.org/600047
git-svn-id: http://src.chromium.org/svn/trunk/src/build@38658 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
file scope.
To resolve bug 33186, I am trying to turn test_shell.gyp into test_shell.gypi,
and have webkit.gyp include it. webkit.gyp is not chromium_code, but the
targets in test_shell.gypi are.
BUG=33186
TEST=builds still work, -Werror and friends are still applied (or not) correctly
Review URL: http://codereview.chromium.org/595010
git-svn-id: http://src.chromium.org/svn/trunk/src/build@38519 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Turned out there is no benefit of having this in a separate git repository.
No code change in candidate_window.cc, but modified the copyright notice
from Chromium OS Authors to Chromium Authors.
Slightly modified text_input.gyp to make it compile.
We'll also change cros_deps/DEPS in a separate CL.
BUG=none
TEST=confirmed candidate_window compiles as before.
Review URL: http://codereview.chromium.org/579026
git-svn-id: http://src.chromium.org/svn/trunk/src/build@38345 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
rsesek@chromium.org
satorux@chromium.org
timurrrr@chromium.org
phajdan.jr@chromium.org
gdk@chromium.org
ben@chromium.org
willchan@chromium.org
joth@chromium.org
mark@chromium.org
piman@chromium.org
evan@chromium.org
davemoore@chromium.org
tony@chromium.org
thestig@chromium.org
nsylvain@chromium.org
zelidrag@chromium.org
bradnelson@google.com
jiesun@google.com
robertshield@chromium.org
agl@chromium.org
nirnimesh@chromium.org
alokp@chromium.org
mmoss@google.com
jorlow@chromium.org
mnaganov@chromium.org