• UNIX/LINUX similar systems
• MACOSX
• WINDOWS

UNIX/LINUX similar systems

Using autotools

It is highly recommended that pkg-config is installed. If needed, you have to properly set the environment variable PKG_CONFIG_PATH so that the .pc files are found.

To build from top-level directory, you can simply type:

./bootstrap.sh
./configure
make

To keep all build files in a separate directory, you can type instead:

./bootstrap.sh
mkdir build
cd build
../configure
make

To install:

sudo make install

To clean:

make clean
make distclean

To build doc (requires 'doxygen' to be found on your system): (this will create an html directory in TOP_LEVEL/doc)

make doc

Main './configure' options (type './configure --help' for more details)

• '--enable-jpip'
• '--enable-mj2'
• '--enable-jpwl'
• '--enable-jpip'
• '--prefix=/path/to/install/directory' (example : '--prefix=$PWD/installed')
• '--enable-debug' (default : disabled)

You can also specify your own CFLAGS and LDFLAGS with (for example):

  CFLAGS="-O3 -pipe" LDFLAGS="-Wl,-s" ./configure

The (optional) dependencies of some binaries are libpng, libtiff, libcms 1 or 2 and FastCGI. Only libtiff and FastCGI have no .pc file. There should be some automatic detection if they are installed in /usr, /usr/local or /opt/local. Otherwise, you can tune their detection (as well as for libpng and libcms1 or 2 too) with the environment variables:

• TIFF_CFLAGS
• TIFF_LIBS
• FCGI_CFLAGS
• FCGI_LIBS

See './configure --help' output for more details.

Using cmake (see www.cmake.org)

Type:

cmake .
make

If you are root:

make install
make clean

else:

sudo make install
make clean

To build doc (requires 'doxygen' to be found on your system): (this will create an html directory in TOP_LEVEL/doc)

make doc

Binaries are located in the 'bin' directory.

Main available cmake flags:

• To specify the install path: '-DCMAKE_INSTALL_PREFIX=/path'
• To build the shared libraries and links the executables against it: '-DBUILD_SHARED_LIBS:bool=on' (default: 'ON')

Note: when using this option, static libraries are not built and executables are dynamically linked.

• To build the CODEC executables: '-DBUILD_CODEC:bool=on' (default: 'ON')
• To build the MJ2 executables: '-DBUILD_MJ2:bool=on' (default: 'OFF')
• To build the JPWL executables and JPWL library: '-DBUILD_JPWL:bool=on' (default: 'OFF')
• To build the JPIP client (java compiler recommended) library and executables: '-DBUILD_JPIP:bool=on' (default: 'OFF')
• To build the JPIP server (need fcgi) library and executables: '-DBUILD_JPIP_SERVER:bool=on' (default: 'OFF')
• To enable testing (and automatic result upload to http://my.cdash.org/index.php?project=OPENJPEG):

cmake . -DBUILD_TESTING:BOOL=ON -DOPJ_DATA_ROOT:PATH='path/to/the/data/directory' -DBUILDNAME:STRING='name_of_the_build'
make
make Experimental

Note : JPEG2000 test files are available with

svn checkout http://openjpeg.googlecode.com/svn/data

If '-DOPJ_DATA_ROOT:PATH' option is omitted, test files will be automatically searched in '${CMAKE_SOURCE_DIR}/../data', corresponding to the location of the data directory when compiling from the trunk (and assuming the data directory has been checked out of course).

Note 2 : to execute the encoding test suite, kakadu binaries are needed to decode encoded image and compare it to the baseline. Kakadu binaries are freely available for non-commercial purposes at http://www.kakadusoftware.com. kdu_expand will need to be in your PATH for cmake to find it.

Using ctest script to perform dashboard submission

You can used ctest command to build the openjepg lib and submit to the dashboard.

ctest -S mymachine_openjpeg.cmake -V

Openjpeg ctest scripts are available with

svn checkout http://openjpeg.googlecode.com/svn/dev-utils

However you need to specify some variables inside the script, so explore the mymachine_openjpeg.cmake file and read the comments. Other files expose the way to perform a nightly submission with different platforms and can provide some tips to create a specific script.

MACOSX

The same building procedures as above (autotools and cmake) work for MACOSX. The xcode project file can also be used.

If it does not work, try adding the following flag to the cmake command :

-DCMAKE_OSX_ARCHITECTURES:STRING=i386

WINDOWS

If you're using cygwin or MinGW+MSYS, the same procedures as for Unix can be used.

Otherwise you can use cmake to generate project files for the IDE you are using (VC2010, etc). Type 'cmake --help' for available generators on your platform.