summaryrefslogtreecommitdiffstats
path: root/build/linux
Commit message (Collapse)AuthorAgeFilesLines
* Exclude platform_data_fetcher_linux.cc on *BSD because of udev specific coderobert.nagy@gmail.com2012-01-091-2/+3
| | | | | | | | | | | | Also disable libudev on *BSD because it's not available. BUG= TEST= Review URL: http://codereview.chromium.org/9147003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@116868 0039d316-1c4b-4281-b951-d872f2087c98
* Add gamepad data fetcher for Linuxscottmg@google.com2012-01-061-0/+21
| | | | | | | | | | BUG=79050 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=116724 Review URL: http://codereview.chromium.org/8899017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@116752 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 116724 - Add gamepad data fetcher for Linuxasvitkine@chromium.org2012-01-061-21/+0
| | | | | | | | | | | | | | Broke ASAN builder: http://build.chromium.org/p/chromium.memory/builders/ASAN%20Builder/builds/8480/steps/update/logs/stdio BUG=79050 Review URL: http://codereview.chromium.org/8899017 TBR=scottmg@google.com Review URL: http://codereview.chromium.org/9110039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@116726 0039d316-1c4b-4281-b951-d872f2087c98
* Add gamepad data fetcher for Linuxscottmg@google.com2012-01-061-0/+21
| | | | | | | | BUG=79050 Review URL: http://codereview.chromium.org/8899017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@116724 0039d316-1c4b-4281-b951-d872f2087c98
* net: rename NSS's 'ssl' to 'libssl'agl@chromium.org2011-12-151-1/+1
| | | | | | | | | | | | | ninja doesn't like there being several targets with the name 'ssl', so I renamed NSS's 'ssl' target to 'libssl'. BUG=none TEST=compiles Review URL: http://codereview.chromium.org/8907043 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@114656 0039d316-1c4b-4281-b951-d872f2087c98
* Fix python scripts in src/build/maruel@chromium.org2011-11-231-2/+5
| | | | | | | | | | | | | | | | | | Make sure that: - shebang is only present for executable files - shebang is #!/usr/bin/env python - __main__ is only present for executable files - file's executable bit is coherent Also fix EOF LF to be only one. TBR=michaelbai@chromium.org BUG=105108 TEST= Review URL: http://codereview.chromium.org/8667008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111385 0039d316-1c4b-4281-b951-d872f2087c98
* Reland with a virtual destructor.dcheng@chromium.org2011-11-101-0/+21
| | | | | | | | | | | | | Use XFixes to update the clipboard sequence number. BUG=73478 TEST=manual testing Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=109528 Review URL: http://codereview.chromium.org/8501002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109537 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 109528 - Use XFixes to update the clipboard sequence number.dcheng@chromium.org2011-11-101-21/+0
| | | | | | | | | | | | BUG=73478 TEST=manual testing Review URL: http://codereview.chromium.org/8501002 TBR=dcheng@chromium.org Review URL: http://codereview.chromium.org/8524014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109530 0039d316-1c4b-4281-b951-d872f2087c98
* Use XFixes to update the clipboard sequence number.dcheng@chromium.org2011-11-101-0/+21
| | | | | | | | | BUG=73478 TEST=manual testing Review URL: http://codereview.chromium.org/8501002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109528 0039d316-1c4b-4281-b951-d872f2087c98
* OpenBSD patches for base / split from CR #8275005mark@chromium.org2011-10-181-6/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | base/base.gypi: - Add native_library_linux.cc to the openbsd build. - Add '..' to include_dirs so that OS_* definitions are available in symbolize.cc base/debug/debugger_posix.cc: - Add support for figuring out if the process is being debugged on OpenBSD by sharing some code with Mac. base/process_util_unittest.cc: - Disable the OutOfMemoryTest on OpenBSD base/third_party/symbolize/symbolize.cc: - Include the correct elf header on OpenBSD build/linux/system.gyp: - The dl library is linux only, so only use it there. BUG= TEST= Review URL: http://codereview.chromium.org/8329023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106078 0039d316-1c4b-4281-b951-d872f2087c98
* aura: Build aura_builder on linux.sadrul@chromium.org2011-10-051-6/+6
| | | | | | | | | | | | | | . aura is never built with gtk anymore. So it's not necesary to disable GTK events in the message-pump. . Make sure glib headers are included when building non-gtk aura. . Update the 'glib' target to include gobject-2.0 and gthread-2.0 packages. BUG=none TEST=aura_builder builds on linux with use_aura=1 Review URL: http://codereview.chromium.org/8144009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104165 0039d316-1c4b-4281-b951-d872f2087c98
* linux: convert more dependencies to 'settings'evan@chromium.org2011-09-231-2/+2
| | | | | | | | BUG=96629 Review URL: http://codereview.chromium.org/7970010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@102523 0039d316-1c4b-4281-b951-d872f2087c98
* Remove 'settings' type from gyp filesevan@chromium.org2011-09-221-19/+19
| | | | | | | | | | | It is not actually supported by gyp; the fact that it works is a bug that I am working on fixing. BUG=96629 Review URL: http://codereview.chromium.org/7889051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@102306 0039d316-1c4b-4281-b951-d872f2087c98
* aura: Make 'ui' buildable without gtk.sadrul@chromium.org2011-09-211-0/+36
| | | | | | | | | BUG=97131 TEST=ui_unittests links and runs with use_aura=1 Review URL: http://codereview.chromium.org/7977025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@102131 0039d316-1c4b-4281-b951-d872f2087c98
* Reland 102005 and 102009: aura: Explicitly disable GTK.sadrul@chromium.org2011-09-211-13/+37
| | | | | | | | | | | | | | | Explicitly disable GTK by setting TOOLKIT_USES_GTK. This is the first in a series of changes required to have chrome on aura build and link without GTK. This CL makes base/ build without GTK. Subsequent CLs will do this for other components. TBR=evan@chromium.org BUG=97131 TEST=none Review URL: http://codereview.chromium.org/7983022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@102058 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 102005 - aura: Explicitly disable GTK.sky@chromium.org2011-09-201-1/+0
| | | | | | | | | | | | | | Explicitly disable GTK by setting TOOLKIT_USES_GTK. This is the first in a series of changes required to have chrome on aura build and link without GTK. This CL makes base/ build without GTK. Subsequent CLs will do this for other components. BUG=97131 TEST=none Review URL: http://codereview.chromium.org/7904034 TBR=sadrul@chromium.org Review URL: http://codereview.chromium.org/7978007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@102015 0039d316-1c4b-4281-b951-d872f2087c98
* aura: Explicitly disable GTK.sadrul@chromium.org2011-09-201-0/+1
| | | | | | | | | | | Explicitly disable GTK by setting TOOLKIT_USES_GTK. This is the first in a series of changes required to have chrome on aura build and link without GTK. This CL makes base/ build without GTK. Subsequent CLs will do this for other components. BUG=97131 TEST=none Review URL: http://codereview.chromium.org/7904034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@102005 0039d316-1c4b-4281-b951-d872f2087c98
* Fourth attempt at the following. Unreviewed, this was originally reviewed ↵pkasting@chromium.org2011-09-151-16/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | in http://codereview.chromium.org/7550002 . Clean up SSL false start blacklist code. Numerous changes, including: * Handle trailing dots in LastTwoLabels() as in http://codereview.chromium.org/7518035/ . Rename this function to LastTwoComponents() to match the terminology used in the RegistryControlledDomainService and elsewhere in Chrome. * Since callers are using std::string anyway, make the functions in the header take const std::string& instead of char*. This also allows doing string operations on them. * Use string operations (like find_last_of()) in place of hand-written algorithms, for brevity, clarity, and safety. * Avoid "unsigned", which the style guide forbids, and use allowed types like size_t, uint32, or int (depending on the situation). * Avoid #define and "using". * Use standard algorithms for similar reasons as using string ops. * Use file_util functions to significantly abbreviate file reading/writing code. * Use wmain() (on Windows) in combination with FilePath to avoid issues if the provided pathname has extended characters that don't flatten losslessly to the default codepage (thanks Darin for pointing out this issue). * Avoid casting where possible. Avoid some casts for printf()-style calls by using a string stream, which also allows for slightly less boilerplate. * Convert non-error uses of stderr to the chrome-standard VLOG(1). * Correctly handle hostnames with trailing dots in the input file. * In general, shorten code where possible. Because this adds a dependency on base, and ssl_false_start_blacklist_process has the "#host" specifier in net.gyp, bradnelson tells me that base and its dependencies need an explicit "host, target" toolchain list for the Linux builds to work correctly. It would be nice if we could avoid this but I guess gyp would have to be smarter or something. BUG=none TEST=none Review URL: http://codereview.chromium.org/7903016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@101378 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 98885 - Third attempt at the following. Unreviewed, this was ↵rsleevi@chromium.org2011-08-311-56/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | originally reviewed in http://codereview.chromium.org/7550002 . Clean up SSL false start blacklist code. Numerous changes, including: * Handle trailing dots in LastTwoLabels() as in http://codereview.chromium.org/7518035/ . Rename this function to LastTwoComponents() to match the terminology used in the RegistryControlledDomainService and elsewhere in Chrome. * Since callers are using std::string anyway, make the functions in the header take const std::string& instead of char*. This also allows doing string operations on them. * Use string operations (like find_last_of()) in place of hand-written algorithms, for brevity, clarity, and safety. * Avoid "unsigned", which the style guide forbids, and use allowed types like size_t, uint32, or int (depending on the situation). * Avoid #define and "using". * Use standard algorithms for similar reasons as using string ops. * Use file_util functions to significantly abbreviate file reading/writing code. * Use wmain() (on Windows) in combination with FilePath to avoid issues if the provided pathname has extended characters that don't flatten losslessly to the default codepage (thanks Darin for pointing out this issue). * Avoid casting where possible. Avoid some casts for printf()-style calls by using a string stream, which also allows for slightly less boilerplate. * Convert non-error uses of stderr to the chrome-standard VLOG(1). * Correctly handle hostnames with trailing dots in the input file. * In general, shorten code where possible. Because this adds a dependency on base, and ssl_false_start_blacklist_process has the "#host" specifier in net.gyp, bradnelson tells me that base and its dependencies need an explicit "host, target" toolchain list for the Linux builds to work correctly. It would be nice if we could avoid this but I guess gyp would have to be smarter or something. BUG=none TEST=none Review URL: http://codereview.chromium.org/7804001 TBR=pkasting@chromium.org Review URL: http://codereview.chromium.org/7778035 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98917 0039d316-1c4b-4281-b951-d872f2087c98
* Third attempt at the following. Unreviewed, this was originally reviewed in ↵pkasting@chromium.org2011-08-301-16/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | http://codereview.chromium.org/7550002 . Clean up SSL false start blacklist code. Numerous changes, including: * Handle trailing dots in LastTwoLabels() as in http://codereview.chromium.org/7518035/ . Rename this function to LastTwoComponents() to match the terminology used in the RegistryControlledDomainService and elsewhere in Chrome. * Since callers are using std::string anyway, make the functions in the header take const std::string& instead of char*. This also allows doing string operations on them. * Use string operations (like find_last_of()) in place of hand-written algorithms, for brevity, clarity, and safety. * Avoid "unsigned", which the style guide forbids, and use allowed types like size_t, uint32, or int (depending on the situation). * Avoid #define and "using". * Use standard algorithms for similar reasons as using string ops. * Use file_util functions to significantly abbreviate file reading/writing code. * Use wmain() (on Windows) in combination with FilePath to avoid issues if the provided pathname has extended characters that don't flatten losslessly to the default codepage (thanks Darin for pointing out this issue). * Avoid casting where possible. Avoid some casts for printf()-style calls by using a string stream, which also allows for slightly less boilerplate. * Convert non-error uses of stderr to the chrome-standard VLOG(1). * Correctly handle hostnames with trailing dots in the input file. * In general, shorten code where possible. Because this adds a dependency on base, and ssl_false_start_blacklist_process has the "#host" specifier in net.gyp, bradnelson tells me that base and its dependencies need an explicit "host, target" toolchain list for the Linux builds to work correctly. It would be nice if we could avoid this but I guess gyp would have to be smarter or something. BUG=none TEST=none Review URL: http://codereview.chromium.org/7804001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98885 0039d316-1c4b-4281-b951-d872f2087c98
* Add glib to system.gyp for cros static library (load.cc)stevenjb@google.com2011-08-291-0/+17
| | | | | | | | | | | An upcoming libcros change adds a header dependency on glib, so we need an entry in system.gyp for cros_api.gyp to reference. BUG=chromium-os:19576 TEST=none Review URL: http://codereview.chromium.org/7799001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98668 0039d316-1c4b-4281-b951-d872f2087c98
* linux: clean up include paths for local nss headersevan@chromium.org2011-08-241-9/+5
| | | | | | | | | | The comment stated that gyp include paths come after cflags, but that is not true: include paths come before cflags. Use the gyp prepend operator just to be extra sure. Review URL: http://codereview.chromium.org/7720016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98071 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 95907 - Clean up SSL false start blacklist code. Numerous changes, ↵mnissler@chromium.org2011-08-111-56/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | including: * Handle trailing dots in LastTwoLabels() as in http://codereview.chromium.org/7518035/ . Rename this function to LastTwoComponents() to match the terminology used in the RegistryControlledDomainService and elsewhere in Chrome. * Since callers are using std::string anyway, make the functions in the header take const std::string& instead of char*. This also allows doing string operations on them. * Use string operations (like find_last_of()) in place of hand-written algorithms, for brevity, clarity, and safety. * Avoid "unsigned", which the style guide forbids, and use allowed types like size_t, uint32, or int (depending on the situation). * Avoid #define and "using". * Use standard algorithms for similar reasons as using string ops. * Use file_util functions to significantly abbreviate file reading/writing code. * Use wmain() (on Windows) in combination with FilePath to avoid issues if the provided pathname has extended characters that don't flatten losslessly to the default codepage (thanks Darin for pointing out this issue). * Avoid casting where possible. Avoid some casts for printf()-style calls by using a string stream, which also allows for slightly less boilerplate. * Convert non-error uses of stderr to the chrome-standard VLOG(1). * Correctly handle hostnames with trailing dots in the input file. * In general, shorten code where possible. Because this adds a dependency on base, and ssl_false_start_blacklist_process has the "#host" specifier in net.gyp, bradnelson tells me that base and its dependencies need an explicit "host, target" toolchain list for the Linux builds to work correctly. It would be nice if we could avoid this but I guess gyp would have to be smarter or something. BUG=none TEST=none Review URL: http://codereview.chromium.org/7550002 TBR=pkasting@chromium.org Review URL: http://codereview.chromium.org/7623015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96391 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 95910 - Revert 95907 - Clean up SSL false start blacklist code.pkasting@chromium.org2011-08-101-16/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Now that r96121 has landed, this should not cause compile failures when compiling base/ on the host. Original comments follow. Numerous changes, including: * Handle trailing dots in LastTwoLabels() as in http://codereview.chromium.org/7518035/ . Rename this function to LastTwoComponents() to match the terminology used in the RegistryControlledDomainService and elsewhere in Chrome. * Since callers are using std::string anyway, make the functions in the header take const std::string& instead of char*. This also allows doing string operations on them. * Use string operations (like find_last_of()) in place of hand-written algorithms, for brevity, clarity, and safety. * Avoid "unsigned", which the style guide forbids, and use allowed types like size_t, uint32, or int (depending on the situation). * Avoid #define and "using". * Use standard algorithms for similar reasons as using string ops. * Use file_util functions to significantly abbreviate file reading/writing code. * Use wmain() (on Windows) in combination with FilePath to avoid issues if the provided pathname has extended characters that don't flatten losslessly to the default codepage (thanks Darin for pointing out this issue). * Avoid casting where possible. Avoid some casts for printf()-style calls by using a string stream, which also allows for slightly less boilerplate. * Convert non-error uses of stderr to the chrome-standard VLOG(1). * Correctly handle hostnames with trailing dots in the input file. * In general, shorten code where possible. Because this adds a dependency on base, and ssl_false_start_blacklist_process has the "#host" specifier in net.gyp, bradnelson tells me that base and its dependencies need an explicit "host, target" toolchain list for the Linux builds to work correctly. It would be nice if we could avoid this but I guess gyp would have to be smarter or something. BUG=none TEST=none Review URL: http://codereview.chromium.org/7550002 TBR=pkasting@chromium.org Review URL: http://codereview.chromium.org/7529035 TBR=fischman@chromium.org Review URL: http://codereview.chromium.org/7587003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96211 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 95907 - Clean up SSL false start blacklist code. Numerous changes, ↵fischman@chromium.org2011-08-081-56/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | including: * Handle trailing dots in LastTwoLabels() as in http://codereview.chromium.org/7518035/ . Rename this function to LastTwoComponents() to match the terminology used in the RegistryControlledDomainService and elsewhere in Chrome. * Since callers are using std::string anyway, make the functions in the header take const std::string& instead of char*. This also allows doing string operations on them. * Use string operations (like find_last_of()) in place of hand-written algorithms, for brevity, clarity, and safety. * Avoid "unsigned", which the style guide forbids, and use allowed types like size_t, uint32, or int (depending on the situation). * Avoid #define and "using". * Use standard algorithms for similar reasons as using string ops. * Use file_util functions to significantly abbreviate file reading/writing code. * Use wmain() (on Windows) in combination with FilePath to avoid issues if the provided pathname has extended characters that don't flatten losslessly to the default codepage (thanks Darin for pointing out this issue). * Avoid casting where possible. Avoid some casts for printf()-style calls by using a string stream, which also allows for slightly less boilerplate. * Convert non-error uses of stderr to the chrome-standard VLOG(1). * Correctly handle hostnames with trailing dots in the input file. * In general, shorten code where possible. Because this adds a dependency on base, and ssl_false_start_blacklist_process has the "#host" specifier in net.gyp, bradnelson tells me that base and its dependencies need an explicit "host, target" toolchain list for the Linux builds to work correctly. It would be nice if we could avoid this but I guess gyp would have to be smarter or something. BUG=none TEST=none Review URL: http://codereview.chromium.org/7550002 TBR=pkasting@chromium.org Review URL: http://codereview.chromium.org/7529035 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@95910 0039d316-1c4b-4281-b951-d872f2087c98
* Clean up SSL false start blacklist code. Numerous changes, including:pkasting@chromium.org2011-08-081-16/+56
| | | | | | | | | | | | | | | | | | | | | | | * Handle trailing dots in LastTwoLabels() as in http://codereview.chromium.org/7518035/ . Rename this function to LastTwoComponents() to match the terminology used in the RegistryControlledDomainService and elsewhere in Chrome. * Since callers are using std::string anyway, make the functions in the header take const std::string& instead of char*. This also allows doing string operations on them. * Use string operations (like find_last_of()) in place of hand-written algorithms, for brevity, clarity, and safety. * Avoid "unsigned", which the style guide forbids, and use allowed types like size_t, uint32, or int (depending on the situation). * Avoid #define and "using". * Use standard algorithms for similar reasons as using string ops. * Use file_util functions to significantly abbreviate file reading/writing code. * Use wmain() (on Windows) in combination with FilePath to avoid issues if the provided pathname has extended characters that don't flatten losslessly to the default codepage (thanks Darin for pointing out this issue). * Avoid casting where possible. Avoid some casts for printf()-style calls by using a string stream, which also allows for slightly less boilerplate. * Convert non-error uses of stderr to the chrome-standard VLOG(1). * Correctly handle hostnames with trailing dots in the input file. * In general, shorten code where possible. Because this adds a dependency on base, and ssl_false_start_blacklist_process has the "#host" specifier in net.gyp, bradnelson tells me that base and its dependencies need an explicit "host, target" toolchain list for the Linux builds to work correctly. It would be nice if we could avoid this but I guess gyp would have to be smarter or something. BUG=none TEST=none Review URL: http://codereview.chromium.org/7550002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@95907 0039d316-1c4b-4281-b951-d872f2087c98
* Adding a Wayland basic toolkitdnicoara@chromium.org2011-07-281-0/+24
| | | | | | | | | | | | | | | | | This is essentially a OO wrapper over the Wayland library. It will be used to add Wayland support for Chrome. This was written with the intent of being as standalone as possible and it should not require any external Chrome dependencies. BUG=None TEST=None R=evan@chromium.org Review URL: http://codereview.chromium.org/7457023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94492 0039d316-1c4b-4281-b951-d872f2087c98
* Add libdbus dependency for Linux.satorux@chromium.org2011-07-221-0/+18
| | | | | | | | | | | | | | This is the first patch for our own D-Bus client library. The D-Bus client code will be placed under 'dbus' on the top level directory More patches will follow. BUG=90036 TEST=try bot to make sure this won't break builds. Review URL: http://codereview.chromium.org/7467031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93658 0039d316-1c4b-4281-b951-d872f2087c98
* touch: Always expect XInput2 availability.sadrul@chromium.org2011-07-221-19/+2
| | | | | | | | | BUG=80790 TEST=touch compiles Review URL: http://codereview.chromium.org/6975045 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93621 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: fix build when libgcrypt is not installed.phajdan.jr@chromium.org2011-07-211-1/+1
| | | | | | | | | | This is upstreaming of Gentoo Linux patch. BUG=none Review URL: http://codereview.chromium.org/7433015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93421 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: revive a mysteriously disabled test and add tests for the GNOME ↵mdm@chromium.org2011-07-191-1/+34
| | | | | | | | | | | | Keyring native backend. In order to make the GNOME Keyring API mockable, I've substituted evil preprocessor macros with a slightly less evil scoping trick, and used it even when linking directly. I'm not sure when password_store_x_unittest fell out of the gyp file, but it hasn't been compiled for some time apparently so it required a bit of cleanup to make it compile. I also did a little unrelated cleanup in the gyp files and fixed typos in password_store_default_unittest. BUG=none Review URL: http://codereview.chromium.org/7396013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93093 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the comments setting emands and vim tab width and expansion variables.tony@chromium.org2011-07-111-6/+0
| | | | | | | | | | | | | | | | | These were added in r28089 (http://codereview.chromium.org/256059) but are unnecessary bloat for everyone to carry around, even those that don't use emacs or vim. In an earlier change, I added editor config files in src/tools/emacs/ and src/tools/vim/ so users of the appropriate editor can source those instead. BUG=none TEST=none Review URL: http://codereview.chromium.org/7310019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92046 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 87315 - Revert 87309 - Second attempt to fix linux redux buildermirandac@chromium.org2011-05-311-5/+11
| | | | | | | | | | | | | | | | | Numerous targets were depending on linux/system.gyp:nss even on the openssl build and the gyp update means it shows up as a link error. BUG=None TEST=Builds with and without use_openssl=1 Review URL: http://codereview.chromium.org/7050040 TBR=joth@chromium.org Review URL: http://codereview.chromium.org/7054041 TBR=mirandac@chromium.org Review URL: http://codereview.chromium.org/6962044 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@87316 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 87309 - Second attempt to fix linux redux buildermirandac@chromium.org2011-05-311-11/+5
| | | | | | | | | | | | | | Numerous targets were depending on linux/system.gyp:nss even on the openssl build and the gyp update means it shows up as a link error. BUG=None TEST=Builds with and without use_openssl=1 Review URL: http://codereview.chromium.org/7050040 TBR=joth@chromium.org Review URL: http://codereview.chromium.org/7054041 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@87315 0039d316-1c4b-4281-b951-d872f2087c98
* Second attempt to fix linux redux builderjoth@chromium.org2011-05-311-5/+11
| | | | | | | | | | | Numerous targets were depending on linux/system.gyp:nss even on the openssl build and the gyp update means it shows up as a link error. BUG=None TEST=Builds with and without use_openssl=1 Review URL: http://codereview.chromium.org/7050040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@87309 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: add gyp rules for gio library and gsettings link mode.mdm@chromium.org2011-05-161-0/+35
| | | | | | | | | | These will be used to add support for proxy settings in gsettings. Note that no new dependencies are added in the default configuration. BUG=80453 Review URL: http://codereview.chromium.org/7030007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85524 0039d316-1c4b-4281-b951-d872f2087c98
* The gyp files don't have a way to refer to POSIX-like OS's as a group, so I ↵mark@chromium.org2011-05-121-2/+2
| | | | | | | | | | | | | | | | defined os_posix, toolkit_gtk, and use_x11 in common.gypi to handle them. I used something similar when porting Chromium 10 and 11 to OpenBSD and Solaris, plus a version of this patch has been tested on FreeBSD. Chromium has also been built on other BSDs, so rather than adding each Unix to every gyp file individually every time another port is added, these broad defines can be used instead and modified with specific logic only where necessary. I included a few modified gyp files so the usage can be seen. I also added sunos5 to some grd/html files and set the default host_arch on i86pc solaris to ia32. BUG=0 TEST={} Patch by ruben <chromium@hybridsource.org>. Review URL: http://codereview.chromium.org/6965007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85154 0039d316-1c4b-4281-b951-d872f2087c98
* Check the ibus version in build script.mark@chromium.org2011-05-021-3/+6
| | | | | | | | | | Patch by Peng Huang <penghuang@chromium.org> BUG=chromium:80972 TEST=Linux desktop Review URL: http://codereview.chromium.org/6893129 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@83758 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: clean up the usage of "use_cups" gyp switch:phajdan.jr@chromium.org2011-04-291-0/+17
| | | | | | | | | | | | | | | | | This CL removes duplication and fixes a build error on system with no CUPS. It uses cups-config instead of hardcoding flags. Also, it removes a superfluous dependency on gcrypt from chrome_browser.gypi. printing uses gcrypt explicitly, but chrome/browser doesn't. It was just blindly copy-pasted. I just extracted libgcrypt target to build/linux/system.gyp, and switched to libgcrypt-config instead of hardcoding flags. BUG=none Review URL: http://codereview.chromium.org/6883221 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@83489 0039d316-1c4b-4281-b951-d872f2087c98
* Remove ibus checking script from views.gyp and add use_ibus=1 optionpenghuang@chromium.org2011-04-271-5/+3
| | | | | | | | | | BUG=chromium:80700 TEST=Test it on Linux desktop Review URL: http://codereview.chromium.org/6904053 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@83232 0039d316-1c4b-4281-b951-d872f2087c98
* OpenBSD: compatibility fixes for the build system.phajdan.jr@chromium.org2011-04-141-4/+4
| | | | | | | | | | | | | - switch from /bin/bash to /bin/sh (bash is not a part of base system on OpenBSD) - switch from /usr/bin/python to /usr/bin/env python (python is not a part of base system on OpenBSD) BUG=none Review URL: http://codereview.chromium.org/6845002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81550 0039d316-1c4b-4281-b951-d872f2087c98
* Add input method support for views and integrate ibus input frameworkoshima@google.com2011-02-121-0/+24
| | | | | | | | | | | BUG=none TEST=tested on Linux desktop oshima landed for penghuang Review URL: http://codereview.chromium.org/6480036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@74709 0039d316-1c4b-4281-b951-d872f2087c98
* Fix libnss include path when building under WebKit on linux to matchadamk@chromium.org2011-01-191-2/+2
| | | | | | | | the new code location under Source/. Review URL: http://codereview.chromium.org/6264004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@71793 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: Remove obsolete dump_signature.py.thestig@chromium.org2010-12-131-56/+0
| | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/5721004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@69058 0039d316-1c4b-4281-b951-d872f2087c98
* Switch linux OpenSSL build to use custom openssl versionjoth@chromium.org2010-12-091-23/+0
| | | | | | | | | | | | This allows us to test experimental library features, and to track a known openssl version. Also bumps OpenSSL 65717:68738, to fix up the default CA root path in the reference library. BUG=None TEST=Still builds & runs! Review URL: http://codereview.chromium.org/5625012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68749 0039d316-1c4b-4281-b951-d872f2087c98
* scons: excise more scons references from the code baseevan@chromium.org2010-12-031-1/+0
| | | | | | | | | | I got to undo some hacks, too! TEST=compiles Review URL: http://codereview.chromium.org/5535003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68119 0039d316-1c4b-4281-b951-d872f2087c98
* Improve pkg-config-wrapper to support ChromiumOS sysrootspiman@google.com2010-11-192-15/+40
| | | | | | | | | | | | | | | | | | | | | | http://codereview.chromium.org/4516002/show had to be reverted because it conflicts with "old style" sysroots that are still used on the arm builders. This is a cleaner approach that should work there. The previous approach assumed that all variables in .pc files were relative to |prefix|. It would be a desirable thing to have but in practice a few packages don't follow this and have already dereferenced |prefix| in other variables (e.g. |libdir|). So instead of forcing |prefix|, this version keeps the original one but strips the path before '/usr' (in |prefix|) from all returned paths before prepending the sysroot path. For example if you have foo.pc: prefix=/build/board/usr libdir=/build/board/usr/lib # instead of libdir=${prefix}/lib Libs: -L${libdir}/foo -lfoo Then instead of forcing prefix=/usr (which doesn't fix |libdir|), we find the path before '/usr' in prefix ('/build/board'), that we strip from the returned -L flag ('/build/board/usr/lib/foo' -> '/usr/lib/foo') before prepending the sysroot path (-> '/path/to/sysroot/usr/lib/foo'). BUG=None TEST=build with sysroot=/path/to/chromiumos/chroot/build/x86-generic Review URL: http://codereview.chromium.org/5105005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66712 0039d316-1c4b-4281-b951-d872f2087c98
* A workaround to close currently opened menu. Send escape key if screen ↵oshima@chromium.org2010-11-181-0/+5
| | | | | | | | | | | | | locker fails to grab input. * added new xtst target in build/linux/system.gyp BUG=chromium-os:5902 TEST=goto youtube, open flash menu then kick off the screen locker. It used to show spinner and eventually crash. It should close the menu and lock, and will not crash. Review URL: http://codereview.chromium.org/5043002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66662 0039d316-1c4b-4281-b951-d872f2087c98
* unit_tests: Fix link error (missing libXi) on Linuxevan@chromium.org2010-11-151-0/+8
| | | | | | | | | | | | | | unit_tests fails to link due to requirement on libXi. This is implicitly provided by 'gdk', but unit_tests does not depend on this target. We add a 'xi' dependency for any target depending on 'x11'. BUG=63209 TEST=None (Landing patch for jknotten@chromium.org.) Review URL: http://codereview.chromium.org/5016001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66169 0039d316-1c4b-4281-b951-d872f2087c98
* touchui: First pass at XInput2 message pump.sadrul@chromium.org2010-11-121-1/+11
| | | | | | | | | | | Capture X events using XInput2. BUG=None TEST=None Review URL: http://codereview.chromium.org/4186004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65959 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-04 00:59:36 +0000