diff options
author | Oliver Smith <osmith@sysmocom.de> | 2018-11-14 11:50:17 +0100 |
---|---|---|
committer | Oliver Smith <osmith@sysmocom.de> | 2018-11-20 17:13:25 +0100 |
commit | fc9426e02ee6a448f22a42b95866a2c91b77fd4e (patch) | |
tree | 657d0fd3174965e5ed97948ca33f213958afc320 /osmo-gsm-manuals.pc.in | |
parent | dec39cdea98804e63e6e6c8361ae4b94d0139ede (diff) |
prepare for autotools: add git-version-gen
Add the same version of git-version-gen, which most other Osmocom
repositories (libasn1c, libosmocore, libosmo-netif, libosmo-sccp, ...)
are using, so they behave the same.
git-version-gen generates a version string derived from the git
repository, or from a .tarball-version file when running outside of a
git directory. Unfortunatelly it seems to be impossible to use
git-version-gen from autoconf without adding it to the source tree.
Autotools will be used to install the shared manual files into the
system in a way that is consistent with the other Osmocom repositories:
$ autoreconf -fi
$ ./configure --prefix=/usr/local
$ make
$ make install
Project repositories will check with pkg-config if osmo-gsm-manuals is
installed (like any other shared Osmocom component), when a new
configure flag for building the manuals is passed. This will also work
with distribution's package managers, for instance we could have a
osmo-gsm-manuals-dev package in Debian on which the other packages
would have a build-time dependency to build the UNIX man pages
(OS#3386).
(moving manuals to project repositories 4/19)
Related: OS#3385
Change-Id: I34b0d20046417179250a5065574e2bc303889cf6
Diffstat (limited to 'osmo-gsm-manuals.pc.in')
0 files changed, 0 insertions, 0 deletions