OpenSystemsDevelopment / qpdf

Commit cb1188e1053ef4e438f8bd2ccf8a3af835ba87d6

Authored by Jay Berkenbilt
1 parent a237e924

Instructions for building from pristine checkout

Inline Side-by-side
Showing 1 changed file with 26 additions and 2 deletions
@@ -76,8 +76,32 @@ That code has the following license: @@ -76,8 +76,32 @@ That code has the following license:
76 SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 76 SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
77 77
78 78
79 -Building on UNIX/Linux  
80 -====================== 79 +Building from a pristine checkout
  80 +=================================
  81 +
  82 +When building qpdf from a pristine checkout from version control,
  83 +documentation and automatically generated files are not present.
  84 +Building on Windows from a pristine checkout is not guaranteed to work
  85 +because of issues running autoconf; see README-windows.txt for how to
  86 +handle this. For UNIX and UNIX-like systems, you must have some
  87 +addditional tools installed to build from the source repository. To
  88 +do this, you should run
  89 +
  90 +./autogen.sh
  91 +./configure --enable-doc-maintenance
  92 +make
  93 +make install
  94 +
  95 +If you don't have Apache fop and the docbook stylesheets installed,
  96 +you won't be able to build documentation. You can omit
  97 +--enable-doc-maintenance and produce working qpdf software that passes
  98 +its test suite, but make install will fail because the documentation
  99 +files won't exist. Depending on your purposes, you can either work
  100 +around this or grab the docs from a source distribution.
  101 +
  102 +
  103 +Building from source distribution on UNIX/Linux
  104 +===============================================
81 105
82 For UNIX and UNIX-like systems, you can usually get by with just 106 For UNIX and UNIX-like systems, you can usually get by with just
83 107