summaryrefslogtreecommitdiff
path: root/build/bootstrap.build
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2017-04-29 08:22:45 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2017-04-29 08:24:16 +0200
commit34b0c86b92ac5f1d3b8b4e7c61d70b8e3f41c2e3 (patch)
treed7a4b0671cb204bd6a696fbaee17de11112453c6 /build/bootstrap.build
parentf17383c18bff2458f4795a822dd1d722c3b839ad (diff)
Bump version to 3.18.0-a.0.z, switch to version module
Diffstat (limited to 'build/bootstrap.build')
-rw-r--r--build/bootstrap.build11
1 files changed, 1 insertions, 10 deletions
diff --git a/build/bootstrap.build b/build/bootstrap.build
index 2a3a219..255b363 100644
--- a/build/bootstrap.build
+++ b/build/bootstrap.build
@@ -3,8 +3,6 @@
project = libsqlite3
-using build@0.4.0
-
# SQLite releases usually have 3-component versions but once in a while they
# will make a 4-component release for what appears to be important bug fixes
# only. So instead of dragging the fourth component around (and confusing a
@@ -13,9 +11,6 @@ using build@0.4.0
#
# See also: https://www.sqlite.org/versionnumbers.html
#
-version = 3.14.1
-revision = 0
-
# The SQLite documentation says that as long as the major version stays the
# same, then it is backwards-compatible. And since we have the major version
# already embedded into the library name, it doesn't make much sense to repeat
@@ -43,11 +38,7 @@ revision = 0
#
abi_major = 1
-dist.package = $project-$version
-
-if ($revision != 0)
- dist.package += +$revision
-
+using version
using config
using dist
using test