Building and Installing libdmtx-----------------------------------------------------------------1. libdmtx - Building the Core Library::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::I haven't taken the time to get autoconf(1) set up for thispackage, and it's not currently designed to install to thenormal library locations (/usr/lib, /usr/local/lib, etc...).Instead, it will build in the source directory and the testand utility programs will reference it from their own sourcedirectories.Because of this oversimplification, however, the build processcan be quite straightforward.  To build libdmtx, simply:   $ make allBut how often does that actually work on the first try,right?  WHEN you get build errors, you should:a) Try "make all" again.  I know, this is stupid.  But   sometimes it works because there is a problem with the   SELinux context that causes the build to break in some   distos.  Usually the actual compile works fine though,   so the error is just an annoyance that is skipped the   second time around.b) If that doesn't work then next you should check that you   have all the necessary packages installed.  See the   "Dependencies" section below for details.c) If you have done these steps and it still won't build then   please post a message to the libdmtx "Help" forum at   http://sourceforge.net/forum/forum.php?forum_id=513654   so that we can review your issue and the solution can be   found by others who are experiencing the same problem.Other make targets include:   $ make static   Build an object file for static linking   $ make test     Build test programs   $ make util     Build utility programs   $ make style    Test code for style issues   $ make tarball  Build a clean & pressed tarball   $ make clean    Remove non-permanent files2. Building the Test Programs: gltest and simpletest::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::The test program directories are located under libdmtx/test.You can just run "make" in either directory to build eitherprogram.  If you already ran "make all" above, then it willtell you there is nothing left to do.  Again, if there areany problems during the build then be sure to check yourpackages against the dependencies listed in the section below.The gltest program uses OpenGL (Mesa) to simulate raw camerainput.  If it successfully finds and decodes a Data Matrixsymbol then it will write the decoded stream to STDOUT.  Theprogram uses the images from the libdmtx/test/test_imagesdirectory, and you can cycle through them by right-clickinganywhere on the open gltest window.The simpletest program is a simple test program.Both programs build dynamically linked to the libdmtx libraryso I provided "run_gltest.sh" and "run_simpletest.sh" scriptsto save you from having to set and export the LD_LIBRARY_PATHevery time.3. Building the Utilities: dmtxread and dmtxwrite::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::The whole "run_program.sh" wrapper script approach doesn't workvery well for dmtxread and dmtxwrite, since they both expectarguments from the command line.  For this reason they arecurrently built with statically linking, unless you specifyotherwise by using the appropriate make target.  Both programshave similar make rules:   $ make static   Build it statically linked   $ make dmtx.o   Build libdmtx as an object file   $ make dynamic  Build it dynamically linked   $ make clean    Remove non-permanent files4. Dependencies::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::The following packages are required to build libdmtx and itsassociated programs:libdmtx:   (none)gltest:   mesa-libGL   mesa-libGL-devel   mesa-libGLU   mesa-libGLU-devel   SDL   SDL-devel   libpng   libpng-develsimpletest:   (none)dmtxread:   libpng   libpng-devel   libtiff   libtiff-develdmtxwrite:   (none)If you have an RPM-based system and you want to test for all ofthese in one shot, you can give it one of these:   $ rpm -q libpng libpng-devel libtiff libtiff-devel mesa-libGL \         mesa-libGL-devel mesa-libGLU mesa-libGLU-devel SDL SDL-devel5. Anything Else?::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::Did I leave anything out?  If you spent hours searching for asolution that you feel should be included in this file, thenplease drop me an email at mike@dragonflylogic.com.