The Open Source Software Project Based on IBM's Visualization Data Explorer
Home Page
Recent News
About OpenDX
Getting Started
The DX Community
Contact Info

All rights reserved.

Compiling OpenDX

OpenDX is a very large application. It involves a lot of time to get set up and compile. Basically, there are two major tasks involved when getting started. The first is to determine what functionality you'd like to add and compile the libraries for the added functionality. Second, work on compiling the OpenDX code. We have set up some notes that can help with both of these tasks.

Compiling companion libraries
Compiling OpenDX

General Information

What is .tar.gz?

Most files on the Internet are packaged up into files called tar balls. To unpack these files so they can be used, you must use the tar command and may need to use the gzip command as well.

If you have gnu tar installed, it is quite easy to unpack a tar ball. With a tar ball named file.tar.gz you issue the command:

tar -zxvf file.tar.gz

This will typically create a directory named "file" that contains the contents of the desired package. However if you do not have gnu tar installed and this command fails, you can issue the following command:

gzip -d -c file.tar.gz | tar xvf -

This will do the same thing, but you have to admit the command is a bit more complicated to remember.

I've got the libraries set up, but OpenDX config doesn't see them.

After doing all the compiling of the libraries, it might be necessary, if using shared libraries, to set up your libraries correctly. Some OSs need to have the LD_LIBRARY_PATH set to use /usr/local/lib, others such as linux need to have /usr/local/lib added to /etc/ and then run ldconfig. Other applications that use libtool such as ImageMagick, may also have been compiled with libraries in different directories--in that case, look in the files such as and see that everything is located correctly.

If you wish to use the full support of JavaDX, you will probably need to have the shared libraries installed. Without them, some functionality will be lost.

You want to live on the edge, get the code from CVS. CVS Notes:

To access the OpenDX CVS, submit the following commands from a CVS client:

     1.cvs -d login 
     2.cvs -d checkout module 
     3.cvs -d logout 
       or, from the working directory: cvs logout 

The CVS login command saves login information in a file in your home directory so that future CVS commands (performed within the checked-out working directory) don't require the -d option.

The anonymous, read-only username is anoncvs. The password is also anoncvs.

The possible values for module are dx (OpenDX codebase), and dxsamples (OpenDX samples).

Once you've logged in, you can use the CVS checkout and update commands to keep your working directory (your checked-out copy of the files) up-to-date.

You can also set environment variables instead of using -d option shown above. For example a cvs session make look like the following:

%setenv CVSROOT
%cvs login
(Loggin in to ... )
CVS password: anoncvs
%cvs checkout dx
%cvs logout

At times as directories are added or if you've used a prior version of the cvs source tree, you may need to send the following cvs update command:

cvs update -A -d dx

If you wish to use a specific branch of cvs (such as the libtool branch), you can update to it once you've checked out the dx module.

cvs update -r libtool dx

To begin the compile with the CVS sourcetree, you will need to perform the following steps. If you are not using gcc and gnu make, then the automake line needs to be given the following options: (--include-deps --add-missing) or (-i -a)

%cd dx
%libtoolize (if using the libtool branch)

This is also set up in a file named CVSMake, you can just issue this command then run configure and make.