libmng 1.0.10
-------------

Added provisional ANG and anIM support, and made some minor bugfixes.

libmng 1.0.9
------------

A number of optimizations in the chunk handling and reader/writer code.
This saves over 20KB on binary footprint!

Also several bugfixes and a couple of patches bring it another step
closer to perfection.... :-)

See CHANGELOG for details.


Y.T.

Gerard


For more information please visit:

The official libmng web-site:
  http://www.libmng.com/

Libmng's community on SourceForge:
  https://sourceforge.net/project/?group_id=5635

The official MNG homepage:
  http://www.libpng.org/pub/mng/

The official PNG homepage:
  http://www.libpng.org/pub/png/

**********************************************************************
**********************************************************************

                ***** this is unmaintained *****

If you happen to find problems with autoconfiguration and building,
I simply cannot help you. I'm looking for a maintainer that doesn't mind
spending a few minutes every now and then on the next release to make sure
things are still in working order.

For the moment all autoconf stuff ahs been moved into unmaintained!!

**********************************************************************
**********************************************************************




Configuration from CVS
======================

If you're using source checked out from CVS, rather than a source
distribution tarball, please be aware that you can use ./autogen.sh in
place of ./configure below.

Because this is a cross-platform project, the source templates for
the autoconf scripts are sequestered in the 'makefiles' directory.
Running './autogen.sh' will copy them into their conventional places at
the lop level. If you already see the files there, you don't need to
worry about this step.

Basic Installation
==================

   These are generic installation instructions.

   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, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

   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 at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

   The file `configure.in' is used to create `configure' by a program
called `autoconf'.  You only need `configure.in' 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.  If you're
     using `csh' on an old version of System V, you might need to type
     `sh ./configure' instead to prevent `csh' from trying to execute
     `configure' itself.

     Running `configure' takes awhile.  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.

  4. Type `make install' to install the programs and any data files and
     documentation.

  5. 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
     all sorts of other programs in order to regenerate files that came
     with the distribution.

Compilers and Options
=====================

   Some systems require unusual options for compilation or linking that
the `configure' script does not know about.  You can give `configure'
initial values for variables by setting them in the environment.  Using
a Bourne-compatible shell, you can do that on the command line like
this:
     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

Compiling For Multiple Architectures
====================================

   You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory.  To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'.  `cd' to the
directory where you want the object files and executables to go and run
the `configure' script.  `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

   If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory.  After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.

Installation Names
==================

   By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

   You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

   In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files.  Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.

   If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

   Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System).  The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

   For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

   There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on.  Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
     CPU-COMPANY-SYSTEM

See the file `config.sub' for the possible values of each field.  If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.

   If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

Sharing Defaults
================

   If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists.  Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Operation Controls
==================

   `configure' recognizes the following options to control how it
operates.

`--cache-file=FILE'
     Use and save the results of the tests in FILE instead of
     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
     debugging `configure'.

`--help'
     Print a summary of the options to `configure', and exit.

`--quiet'
`--silent'
`-q'
     Do not print messages saying which checks are being made.  To
     suppress all normal output, redirect it to `/dev/null' (any error
     messages will still be shown).

`--srcdir=DIR'
     Look for the package's source code in directory DIR.  Usually
     `configure' can determine that directory automatically.

`--version'
     Print the version of Autoconf used to generate the `configure'
     script, and exit.

`configure' also accepts some other, not widely useful, options.

Configuration options in libmng
===============================

The library is fairly configurable through the use of a number of defines.
Please note however that certain defines are for internal use only.
The following list gives a summary of options that can be used externally to
define the functionality of the library:

========================================

#define MNG_BUILD_DLL

This is used to indicate that a "standard" DLL should result from compiling
the library. Please note the remarks in README.dll if you intend to work
with the library as a DLL. The purpose of this option is to ensure that
DLL builds have the same set of functions.

#define MNG_BUILD_SO

This is used to indicate that a "standard" shared library (SO) should result
from a compilation. The purpose of this option is to ensure that all
shared libraries generated this way will have the same set of functions.

#define MNG_USE_DLL / #define MNG_USE_SO

These should be used when including the library header in the compilation
of an application to indicate that the compiler/linker must take the
necessary steps to make the binary executable to use the standard DLL
or shared library (SO).

#define MNG_SKIP_ZLIB / #define MNG_SKIP_LCMS / #define MNG_SKIP_IJG6B

Use these in conjunction with MNG_USE_DLL / MNG_USE_SO. This is useful if
you only need the external definitions of the MNG library and not the others,
which will speed up the compilation process.

#define MNG_SUPPORT_FULL / #define MNG_SUPPORT_LC / #define MNG_SUPPORT_VLC

These can be used to indicate the level of MNG spec compliance required.
Currently only full MNG compliance is supported.

#define MNG_SUPPORT_IJG6B

This can be used to indicate if JNG support is required. This option will
include the IJG JPEG-library. Note that MNG_SUPPORT_FULL will automatically
set this option. Use this only if you need JNG support with MNG-(V)LC.

#define MNG_FULL_CMS / #define MNG_GAMMA_ONLY / #define MNG_NO_CMS /
#define MNG_APP_CMS

These indicate the color-correction support level of the library.
If you are on a platform that supports lcms (Little CMS by Marti Maria Saguar)
then it is highly recommended to define MNG_FULL_CMS.
If your platform has it's own CMS then select MNG_APP_CMS and be sure to
include the appropriate callbacks in your app.
In all other cases it is recommended to define MNG_GAMMA_ONLY.

#define MNG_SUPPORT_READ / #define MNG_SUPPORT_WRITE /
#define MNG_SUPPORT_DISPLAY

These indicate the high-level support for reading, writing and/or
displaying files. Note that in order to display a file, you'll need to read
it first. (yes, really!)

#define MNG_STORE_CHUNKS

This indicates that the library should store chunk-information when reading
a file. This information can then be processed through the
MNG_ITERATE_CHUNKS() function. Note that you must specify this option if
you want to create and write a new file.

#define MNG_ACCESS_CHUNKS

This is used to indicate that the app may need access to internally stored
chunk information. MNG_STORE_CHUNKS must be defined as well for this option
to function properly.

#define MNG_INTERNAL_MEMMNGMT

You can use this to have the library handle it's own memory allocation and
deallocation through the "standard" memory functions. This option is turned
off by default, which means your app must define the memory callbacks.

#define MNG_ERROR_TELLTALE

Set this on to allow human-readable error-messages to be included in the
library and the error function and callback.

#define MNG_BIGENDIAN_SUPPORTED

This option should be used to indicate the hardware is based on big endian
integers.

#define MNG_SUPPORT_TRACE / #define MNG_TRACE_TELLTALE

These two can be used when debugging an app. You'll need to have the trace
callback setup also. This allows for a rather thorough investigation of the
libraries function paths.

========================================

Any other optional defines you may encounter are for internal use only.
please do not specify them externally. In case of doubt, consult the
support email lists. More info can be found on http://www.libmng.com

The contrib directory contains contributions made by fellow
enthousiasts. (Check respective web-sites for the latest version)

----------------------------------------------------------------------

mngplg - A Netscape plugin for MNG - by Jason Summers

http://pobox.com/~jason1/imaging/mngplg/

The very first contribution, and what a start!
GIF look out, MNG is on the prowl and ready to swat you like a fly!

----------------------------------------------------------------------

mngplay - An SDL based MNG viewer - by Ralph Giles

http://snow.ashlu.bc.ca/~giles/mng/

Another nice contribution. View MNG files on practically any platform
with this standalone viewer.
Source-code only; Requires SDL library and libmng.so

(Modified by Greg Roelofs)

----------------------------------------------------------------------

mngview - A BCB port of the Delphi sample - by Andy Protano

I have added this nice little port to the BCB samples directory.
It adds a nifty progressbar while reading a file. Excellent work!
Requires libmng.dll
(note: this is in the BCB samples directory)

----------------------------------------------------------------------

mngdump - A BCB GUI-based dump utility - by Andy Protano

Andy has sent me this fully functional MNG dump utility, that gives
detailed information of the contents of any MNG file.
Requires libmng.dll

----------------------------------------------------------------------

mng-view - A GTK-based MNG viewer - by Vova Babin

Vova has been hacking away with the libmng code and has come up with
this nice little sample how to write a MNG viewer using GTK.
Thanks mate!
Source-code only
Requires GTK+ (1.2 or higher) and libmng (0.9.2 or higher)

(Modified by Greg Roelofs)

----------------------------------------------------------------------

mngview - Another MNG viewer; this one for MSVC - by Nicholaus Brennig

A welcome contribution from Nicholaus. Author of SlowView. A very nice
image-handling utility for Windows. A welcome contribution since there
have been numerous questions about linking libmng with MSVC.
Well, look no further. Here it is!

----------------------------------------------------------------------

MSVC libmng project - An MSVC project to build libmng.dll
                    - by Chad Austin

Chad has contributed some project-files that you could use to build
libmng.dll with MSVC. Please be sure to read the README file included.

----------------------------------------------------------------------

fbmngplay - A simple fbcon based mng player - by Stefan Reinauer

Stefan has contributed this little example, based on Ralph's
SDL player. It uses the kernel framebuffer device to display mng
animations through the libmng interface.
(currently for 16-bit buffers only)

----------------------------------------------------------------------

xmngview - Lesstif/Motif standalone player for MNG files
         - by Winfried Szukalski

Winfried contributed this MNG player for X-based systems.
(recently updated)

----------------------------------------------------------------------

makemng - A delta-MNG creation utility for MSVC - by Alex Volkov

Alex sent me this nice utility that will allow you to create highly
optmized MNGs using the delta-PNG capabilities of MNG.

----------------------------------------------------------------------

The samples are in platform-specific directories.

!!! contributions are very welcome !!!


bcb - Borland C++ Builder (3.0) (found under bcb/xxx)
-----------------------------------------------------

win32dll - sample project to create a Windows dll. Requires zlib1.2.1,
           IJG jpgsrc6b and lcms1.0.14. The directories containing these
           libraries must be at the same level as the libmng directory.
           So if you're in the directory with this file and the libmng
           sources, they should be in ..\zlib , ..\jpgsrc6b and ..\lcms
           respectively.

!!!        To run the other Win32 samples you need to copy the libmng.dll
           file from here into the sample's directory !!!

mngtree  - sample project to create a little command-line tool that dumps
           the chunk-structure of a given file onto stdout.

bogus    - a completely bogus example on how to create a perfectly valid
           (though slightly biased) MNG.

mngview  - port of the Delphi mngview sample. contributed by Andy Protano.
           see also README.contrib

mngrepair- an example on how to fix invalid MNG files
           uses the new mng_copy_chunks() function and MNG_SOFTERRORS to
           'ignore' certain input-errors. This conditional *MUST* only be used
           for exactly this kind of software; eg. repair utilities.


delphi - Borland Delphi (3.0+) (found under contrib/delphi/xxx)
---------------------------------------------------------------

mngview  - sample project for a simple mng-viewer. The general unit in
           the delphi directory was translated from libmng.h It can be
           used in other projects to access libmng.dll created with the
           win32dll example above.


unix - Unix (found under contrib/gcc/xxx)
-----------------------------------------

mngtree  - basically a copy of the BCB sample. It includes a makefile for
           Linux and it's been tested on RedHat6.2

/*
   You can use one or more of the following defines to
   reduce the size of the compiled library.  Define the
   SKIPCANVAS macros for any canvas configurations that
   your application doesn't use.  Define the SKIPCHUNK
   macros for any chunks that your application doesn't
   process.  Define MNG_OPTIMIZE_FOOTPRINT to choose
   smaller code size over faster execution and less memory
   usage.  These macros became available in version 1.0.6.
*/

/* eliminate unused features from libmng */
#define MNG_OPTIMIZE_FOOTPRINT
#define MNG_OPTIMIZE_OBJCLEANUP
#define MNG_OPTIMIZE_CHUNKINITFREE
#define MNG_OPTIMIZE_CHUNKASSIGN
#define MNG_OPTIMIZE_CHUNKREADER

#define MNG_SKIPCANVAS_ABGR8
#define MNG_SKIPCANVAS_ARGB8
#define MNG_SKIPCANVAS_BGR8
#define MNG_SKIPCANVAS_BGRA8
#define MNG_SKIPCANVAS_BGRA8_PM
#define MNG_SKIPCANVAS_BGRX8
#define MNG_SKIPCANVAS_RGBA8
#define MNG_SKIPCANVAS_BGR565
#define MNG_SKIPCANVAS_RGB565
#define MNG_SKIPCANVAS_BGRA565
#define MNG_SKIPCANVAS_RGBA565

#define MNG_SKIPCHUNK_iCCP
#define MNG_SKIPCHUNK_tEXt
#define MNG_SKIPCHUNK_zTXt
#define MNG_SKIPCHUNK_iTXt
#define MNG_SKIPCHUNK_bKGD
#define MNG_SKIPCHUNK_pHYs
#define MNG_SKIPCHUNK_sBIT
#define MNG_SKIPCHUNK_sPLT
#define MNG_SKIPCHUNK_hIST
#define MNG_SKIPCHUNK_tIME
#define MNG_SKIPCHUNK_eXPI
#define MNG_SKIPCHUNK_fPRI
#define MNG_SKIPCHUNK_nEED
#define MNG_SKIPCHUNK_pHYg

Packaging Libmng for distribution
---------------------------------

These are some notes for those building binaries for distribution.

We're interested to hear about anywhere libmng is helpful, so let us
know if you're including it with your application or OS. Also, if your
build is publicly accessible, we'd be happy to link to it from
the libmng site.

However, We respectfully request that you *not* distribute binaries as a
shared library (DLL) with any of the major features disabled. While
there is support for this in terms of #ifdef directives (in
libmng_conf.h) and autoconf switches they are intended for embedded
application and testing. The default compilation options support the
full MNG specification, and we wish to avoid the confusion among
general users that partial support would engender.


Platform specific notes:

We have a basic .spec file for generating rpms. Send us a note if you'd
like to clean it up.