We already have a variable for tracking the system libdir name in the
gyp files, so let's use that instead of hardcoding the logic based on
the arch.
BUG=chromium:219015
TEST=`cbuildbot amd64-generic-tot-chrome-pfq-informational` works
Review URL: https://codereview.chromium.org/244593002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@272792 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Speculative revert because we think this might have caused Mac Build bot
failure "gyp: Call to 'python ../../../build/mac/find_sdk.py 10.6' returned exit status -9."
> ozone: Add egltest platform
>
> This supports testing rendering using EGL. Creation of the
> EGLNativeWindowType is punted to a separate library, which has an
> interface defined in eglplatform_shim.h.
>
> TEST=content_shell --ozone-platform=egltest --ignore-gpu-blacklist
> BUG=none
> NOTRY=true
>
> Review URL: https://codereview.chromium.org/288603002TBR=spang@chromium.org
Review URL: https://codereview.chromium.org/288013002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@270474 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This supports testing rendering using EGL. Creation of the
EGLNativeWindowType is punted to a separate library, which has an
interface defined in eglplatform_shim.h.
TEST=content_shell --ozone-platform=egltest --ignore-gpu-blacklist
BUG=none
NOTRY=true
Review URL: https://codereview.chromium.org/288603002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@270471 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The status quo was unmaintainable. These 'component build specific .isolate
files' are superseeded by tools/isolate_driver.py which packages dynamic
libraries automatically.
The new way is much more sane and dynamic, isolate_driver.py is currently very
crude but 'does the job', the expected way to make it work is to read the .ninja
files to extract all the dynamic libraries marked as a dependency to the main
target being executed.
TBR=csharp@chromium.org
BUG=333473
Review URL: https://codereview.chromium.org/226123004
git-svn-id: http://src.chromium.org/svn/trunk/src/build@261871 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Since r257419, linker warning starts to cause the build failure.
This CL is fixing some linker warnings on cross compilation build so that build with target_arch=ia32 option works properly.
Here are the error logs:
/usr/bin/ld: skipping incompatible /lib/x86_64-linux-gnu/libgcrypt.so when searching for -lgcrypt
/usr/bin/ld: skipping incompatible /lib/x86_64-linux-gnu/libgcrypt.a when searching for -lgcrypt
/usr/bin/ld: skipping incompatible /lib/x86_64-linux-gnu/libcap.so when searching for -lcap
/usr/bin/ld: skipping incompatible /lib/x86_64-linux-gnu/libcap.a when searching for -lcap
/usr/bin/ld: warning: libgnutls.so.26, needed by /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib32/libcups.so, may conflict with libgnutls.so.28
BUG=n/a
TEST=build with GYP_DEFINES=target_arch=ia32, run trybot.
Review URL: https://codereview.chromium.org/202633008
git-svn-id: http://src.chromium.org/svn/trunk/src/build@259463 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Right now when supplying a 32-bit sysroot via the 'sysroot' GYP flag on a 64-bit host arch,
pkg-config (and pkg-config-wrapper) fail to generate the correct 32-bit paths within that sysroot.
The solution is to chroot into that directory and run pkg-config from there.
This is intended to work with schroot scripts like 'precise32' generated when running build/install-chroot.sh
BUG=324207
R=piman@chromium.org
Review URL: https://codereview.chromium.org/163583003
git-svn-id: http://src.chromium.org/svn/trunk/src/build@251353 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
chrome/browser/extensions/extension_commands_global_registry_apitest.cc,
which is linked into interactive_ui_tests, uses some functions from libXtst
and thus should declare a dependency on xtst. The only other file that uses
the XTest.h header is in remoting, which declares an xtst dependency already.
This lets us drop the dependency from glib on xtst since most targets don't need
it.
R=phajdan.jr
BUG=339518
Review URL: https://codereview.chromium.org/153893011
git-svn-id: http://src.chromium.org/svn/trunk/src/build@250585 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This converts the remaining targets that depend on X11 libraries over to
depending on targets from build/linux/system.gyp instead of adding the
libraries manually to the link line. This ensures that the link line is
generated with pkg-config and makes the dependencies a bit tighter by
getting rid of the all_dependent_settings entry in ui/ui.gyp
BUG=339518
Review URL: https://codereview.chromium.org/151713003
git-svn-id: http://src.chromium.org/svn/trunk/src/build@250311 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This sets up gyp targets for the various X11 libraries we use and uses
pkg-config to determine the correct cflags/ldflags incantations to use to
link against them instead of listing out -lXfoo lines in libraries sections
in gyp targets throughout the tree. This is more likely to generate the right
lines and makes the dependencies a bit more explicit.
BUG=339518
Review URL: https://codereview.chromium.org/153223002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@248939 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The `file` program follows POSIX as outlined here:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/file.html
Specifically, this part causes troubles:
If the file named by the file operand does not exist, cannot be read, or
the type of the file named by the file operand cannot be determined, this
shall not be considered an error that affects the exit status.
With older versions of `file` (that does not conform to POSIX), this
script will exit 0 with "unknown" as its output when "$1" does not exist.
But with recent releases (that conform to POSIX), this script will exit 1
and can break the build.
Have the script explicitly check for the existence of $1 and if it does
not exist, then runt he unknown logic like normal.
BUG=chromium:332547
TEST=ran python_arch.sh on bogus files with new & old `file` programs
Review URL: https://codereview.chromium.org/137433002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@244778 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The dependency is unnecessary and causes build error in the standalone webrtc project due to missing base.gyp when SCTP is enabled (it depends on usrsctp.gyp, which depends on system.gyp). All system.typ needs from base.gyp is the "include_dirs" pointing to ".." relative to "base". So we can remove the dependency on base.gyp and add "include_dirs":["../.."] instead.
BUG=
Review URL: https://codereview.chromium.org/128933005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@243863 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
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
The GpsLocationProvider is not actually used anywhere, and has most likely bit
rotted after years of no maintenance. It is brittle code written for a
specific version (3.1) of gpsd that is now outdated.
The only Chrome version that had this feature enabled (ChromeOS) makes no use
of it as no hardware was ever shipped that used GPS.
TBR=jam,brettw
Review URL: https://codereview.chromium.org/25752005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@227104 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The linux_aura port didn't deal with multiple monitors very well because
it was treating the X root window as one big display. When xrandr is
present, get the screen areas from it, and exposes this data back to
chrome.
This patch also factors out the EDID parser than chromeos was using into
a common directory. Like chromeos, we use it to assign stable display
IDs.
BUG=287972
R=brettw@chromium.org, derat@chromium.org, sky@chromium.org
Review URL: https://codereview.chromium.org/23536057
git-svn-id: http://src.chromium.org/svn/trunk/src/build@225054 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This adds a g_type_init() call to the beginning of the test,
apparently needed for GLib version earlier than 2.36.
Original change:
linux: Avoid leak in PlatformFontPangoTest.FamilyList.
Call FcFini() at the end of the test to prevent FontConfig
from leaking memory.
BUG=114750
TBR=sky@chromium.org,behdad@chromium.org
Review URL: https://chromiumcodereview.appspot.com/20910002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@214638 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Sometimes ld.so.conf has pattern include like "include ld.so.conf.d/*.conf",
but there is no files that match pattern. In this case "for" loop in process_ld_so_conf
function fails with error "No such file or directory".
This patch uses "ls" to check that pattern matches at least one file.
BUG=none
Review URL: https://chromiumcodereview.appspot.com/19044004
git-svn-id: http://src.chromium.org/svn/trunk/src/build@214230 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
plundblad@chromium.org
vapier@chromium.org
vrk@chromium.org
spang@chromium.org
sadrul@chromium.org
joone.hur@intel.com
thestig@chromium.org
sbc@chromium.org
maruel@chromium.org
hidehiko@chromium.org
glider@chromium.org
petarj@mips.com
kalyan.kondapally@intel.com
jamesr@chromium.org
elan.ruusamae@gmail.com
phajdan.jr@chromium.org
rsleevi@chromium.org
hinoka@google.com
jiayl@chromium.org
thakis@chromium.org
jln@chromium.org
dnicoara@chromium.org
mvanouwerkerk@chromium.org
erg@chromium.org
derat@chromium.org
sl.ostapenko@samsung.com
mallinath@chromium.org