summaryrefslogtreecommitdiffstats
path: root/third_party/sqlite
diff options
context:
space:
mode:
authorshess <shess@chromium.org>2015-08-06 17:10:52 -0700
committerCommit bot <commit-bot@chromium.org>2015-08-07 00:11:23 +0000
commit924597ba8b5def174aebdc96368545f51df1bee2 (patch)
tree7ccb1067b46a00ef5098642ba93863add4d32aed /third_party/sqlite
parent071a5d0dcd53d5719a396fe0f66b8f26943d3744 (diff)
downloadchromium_src-924597ba8b5def174aebdc96368545f51df1bee2.zip
chromium_src-924597ba8b5def174aebdc96368545f51df1bee2.tar.gz
chromium_src-924597ba8b5def174aebdc96368545f51df1bee2.tar.bz2
[sql] Remove _HAS_EXCEPTIONS=0 from build info.
AFAICT, this comes from the original Chrome check-in. AFAICT, it's either not useful, or is redundent WRT the common build files. BUG=none Review URL: https://codereview.chromium.org/1277763003 Cr-Commit-Position: refs/heads/master@{#342237}
Diffstat (limited to 'third_party/sqlite')
-rw-r--r--third_party/sqlite/BUILD.gn1
-rw-r--r--third_party/sqlite/sqlite.gyp3
2 files changed, 0 insertions, 4 deletions
diff --git a/third_party/sqlite/BUILD.gn b/third_party/sqlite/BUILD.gn
index 7f8328d..afdea6e 100644
--- a/third_party/sqlite/BUILD.gn
+++ b/third_party/sqlite/BUILD.gn
@@ -22,7 +22,6 @@ source_set("sqlite") {
"SQLITE_SECURE_DELETE",
"SQLITE_SEPARATE_CACHE_POOLS",
"THREADSAFE",
- "_HAS_EXCEPTIONS=0",
]
if (is_chromeos) {
defines += [
diff --git a/third_party/sqlite/sqlite.gyp b/third_party/sqlite/sqlite.gyp
index 96c867d..bb3a7f5 100644
--- a/third_party/sqlite/sqlite.gyp
+++ b/third_party/sqlite/sqlite.gyp
@@ -28,9 +28,6 @@
# appropriately. Chromium doesn't configure SQLite for that, and would
# prefer to control distribution to worker threads.
'SQLITE_MAX_WORKER_THREADS=0',
- # TODO(shess): Figure out why this is here. Nobody references it
- # directly.
- '_HAS_EXCEPTIONS=0',
# NOTE(shess): Some defines can affect the amalgamation. Those should be
# added to google_generate_amalgamation.sh, and the amalgamation
# re-generated. Usually this involves disabling features which include