Cleanup versioning strategy relanding (#989) (#997)
authorJordan Bayles <jophba@chromium.org>
Wed, 14 Aug 2019 05:41:43 +0000 (22:41 -0700)
committerGitHub <noreply@github.com>
Wed, 14 Aug 2019 05:41:43 +0000 (22:41 -0700)
commit7b28698c5cd00c432cb1b981891b076dd81cd204
treea8fddd50be86e53819e70be1f4cbb0a48086dc3e
parent0d27381acfdd458e802ef59a1304fab356acd652
Cleanup versioning strategy relanding (#989) (#997)

* Cleanup versioning strategy

Currently, versioning is a mess. CMake and Meson have seperate build
version number storage locations, with no way of knowing you need to
have both. Plus, due to recent revisions the amalgamate script is broken
unless you build first, and may still be broken afterwards.

This PR fixes some issues with versioning, and adds comments clarifying
what has to be done when doing a release.

* Run clang format

* Update SOVERSION....
12 files changed:
.gitignore
CMakeLists.txt
CONTRIBUTING.md
amalgamate.py [changed mode: 0644->0755]
doc/jsoncpp.dox
include/CMakeLists.txt
include/json/reader.h
include/json/version.h [new file with mode: 0644]
meson.build
src/lib_json/CMakeLists.txt
src/lib_json/version.h.in [deleted file]
version.txt [deleted file]