[utilities COMMIT] in /cpp-log4shib/trunk: INSTALL Makefile.am autogen.sh configure.ac configure.in include/config.h....

[noreply at shibboleth.net]

Author: scantor
Date: Wed May  8 22:55:07 2013
New Revision: 399

URL: http://svn.shibboleth.net/view/utilities?rev=399&view=rev
Log:
Bump version, cleanup configure script and makefiles

Added:
    cpp-log4shib/trunk/configure.ac
      - copied, changed from r397, cpp-log4shib/trunk/configure.in
Modified:
    cpp-log4shib/trunk/INSTALL
    cpp-log4shib/trunk/Makefile.am
    cpp-log4shib/trunk/autogen.sh
    cpp-log4shib/trunk/configure.in
    cpp-log4shib/trunk/include/config.h.in
    cpp-log4shib/trunk/include/log4shib/config-win32.h
    cpp-log4shib/trunk/msvc10/log4shibDLL/log4shibDLL.rc
    cpp-log4shib/trunk/src/Makefile.am
    cpp-log4shib/trunk/tests/Makefile.am

Modified: cpp-log4shib/trunk/INSTALL
URL: http://svn.shibboleth.net/view/utilities/cpp-log4shib/trunk/INSTALL?rev=399&r1=398&r2=399&view=diff
==============================================================================
--- cpp-log4shib/trunk/INSTALL (original)
+++ cpp-log4shib/trunk/INSTALL Wed May  8 22:55:07 2013
@@ -1,2 +1,370 @@
-See 'Building Log4cpp' section of HTML documentation.
-
+Installation Instructions
+*************************
+
+Copyright (C) 1994-1996, 1999-2002, 2004-2012 Free Software Foundation,
+Inc.
+
+   Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved.  This file is offered as-is,
+without warranty of any kind.
+
+Basic Installation
+==================
+
+   Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package.  The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.  Some packages provide this
+`INSTALL' file but do not implement all of the features documented
+below.  The lack of an optional feature in a given package is not
+necessarily a bug.  More recommendations for GNU packages can be found
+in *note Makefile Conventions: (standards)Makefile Conventions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+   It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring.  Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'.  You need `configure.ac' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
+
+   The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.
+
+     Running `configure' might take a while.  While running, it prints
+     some messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package, generally using the just-built uninstalled binaries.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.  When installing into a prefix owned by root, it is
+     recommended that the package be configured and built as a regular
+     user, and only the `make install' phase executed with root
+     privileges.
+
+  5. Optionally, type `make installcheck' to repeat any self-tests, but
+     this time using the binaries in their final installed location.
+     This target does not install anything.  Running this target as a
+     regular user, particularly if the prior `make install' required
+     root privileges, verifies that the installation completed
+     correctly.
+
+  6. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get

[... 433 lines stripped ...]