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
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
Release Reminders
=================
* Check all open issues in the sourceforge trackers.
* If any interfaces were added or changed, check C API to see whether
changes are appropriate there as well.
* Increment shared library version information as needed
(libqpdf/build.mk)
* Update release notes in manual -- look at diffs and ChangeLog
* Add a release entry to ChangeLog
* Make sure version numbers are consistent in the following
locations:
configure.ac
qpdf.spec
libqpdf/QPDF.cc
manual/qpdf-manual.xml
make_dist verifies this consistency.
* Update release date in manual/qpdf-manual.xml
* Check TODO file to make sure all planned items for the release are
done or retargeted.
* Each year, update copyright notices. Just search for Copyright.
Last updated: 2011.
* To construct a source distribution from a pristine checkout,
make_dist does the following:
./autogen.sh
./configure --enable-doc-maintenance --enable-werror
make build_manual
make distclean
* To create a source release, do an export from the version control
system to a directory called qpdf-version. From the parent of that
directory, run make_dist with the directory as an argument.
Remember to have fop in your path. For internally testing
releases, you can run make_dist with the --no-tests option.
* To create a source release of external libs, do an export from the
version control system into a directory called qpdf-external-libs
and just make a zip file of the result called
qpdf-external-libs-src.zip. See the README.txt file there for
information on creating binary external libs releases.
* To create Windows binary releases, extract the qpdf source
distribution in Windows (MSYS + MINGW, MSVC). From the extracted
directory, extract the binary distribution of the external
libraries. Run ./make_windows_releases from there. You will need
to have zip in your path.
* Remember to copy README-what-to-download.txt separately onto the
download area and make it the default for Windows platforms.
* Remember to update the web page including putting new documentation
in the "files" subdirectory of the website on sourceforge.net.
* Create a tag in the version control system, and make backups of the
actual releases.
* When releasing on source forge, external-libs distributions go in
external-libs/yyyymmdd, and qpdf distributions go in qpdf/vvv
General Build Stuff
===================
QPDF uses autoconf and libtool but does not use automake. The only
files distributed with the qpdf source distribution that are not
controlled are "configure", "libqpdf/qpdf/qpdf-config.h.in",
"aclocal.m4", and some documentation. See above for the steps
required to prepare a source distribution.
A small handful of additional files have been taken from autotools
programs. These should probably be updated from time to time.
* config.guess, config.sub, ltmain.sh, and the m4 directory: these
were created by running libtoolize -c. To update, run libtoolize
-f -c or remove the files and rerun libtoolize.
* Other files copied as indicated:
cp /usr/share/automake-1.11/install-sh .
cp /usr/share/automake-1.11/mkinstalldirs .
The entire contents of the m4 directory came from libtool.m4. If we
had some additional local parts, we could also add those to the m4
directory. In order for this to work, it is necessary to run "aclocal
-I m4" before running autoheader and autoconf.
If building or editing documentation, configure with
--enable-doc-maintenance. This will ensure that all tools or files
required to validate and build documentation are available.
If you want to run make maintainer-clean or make distclean and you
haven't run ./configure, you can pass CLEAN=1 to make on the command
line to prevent it from complaining about configure not having been
run.
|
