README.dev


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

Source code from the git repository
-----------------------------------

To compile source code obtained from the git repository,
make sure you have installed the autoconf, automake and libtool packages.
Execute:

$ autoreconf -i
$ ./configure
$ make
$ make check

Required versions:
* autoconf >= 2.61
* automake >= 1.11.6
* libtool >= 2.4.3

Creating a new release
----------------------

1) Check the version number in configure.ac ("AC_INIT (mpc, _version_...)"),
   INSTALL, src/get_version.c, src/mpc.h (remove suffix "dev" in
   MPC_VERSION_STRING) and Makefile.vc.
2) Verify that the ABI version in src/Makefile.am is correct.
   Check that the executables are not read-only
   (https://lists.gforge.inria.fr/pipermail/mpc-discuss/2020-June/001539.html)
3) Check that NEWS, BUGS and TODO are up to date, and that the minimal
   version numbers of gmp and mpfr in configure.ac, INSTALL and
   doc/mpc.texi are correct.
4) Execute "autoreconf -vfi; touch doc/mpc.texi; make distcheck".
   This updates the files in build-aux and the date and version number in
   doc/version.texi and creates the tarball for distribution.
5) Upload to GNU ftp server.
6) Update the web page on the server.
   The html documentation is created with
      makeinfo --html --no-split mpc.texi
   and the resulting mpc.html is copied to content_html.php.
7) Create a git tag:
   git tag VERSION
8) After the release, update the version number in configure.ac, INSTALL,
   src/get_version.c, src/mpc.h and Makefile.vc.
9) Commit the changes to git.