Installing LCIO on a Machine without Java

To build and install LCIO, you will normally need a full installation of the Java Software Development Kit (Java SDK). This is because – for reasons of streamlining the C++ and Java implementations of LCIO – the required header files are auto-generated from some abstract source when LCIO is built. The bad thing is that this is done by a Java tool named ant, so you have no way to get around Java, even if you are not at all interested in the Java version of LCIO itself. Note that the usual Java Runtime Environment (which might come preinstalled on your machine if you have a resonably recent system version) will not be sufficient.

This means you cannot install LCIO if you don’t have any access to the Java SDK, but at least you can perform the first step of the build process (generation of the C++ header files) on one machine, and then do the rest (compiling, linking, installation) on another machine. Keep in mind that it’s usually not a good idea to copy executable code that has already been compiled and linked (i. e. static or shared libraries) from one machine to another machine with a different system or compiler version.

Another possibility is to copy a complete LCIO installation from one host (e. g. from the AFS installation of the ILC software at DESY), remove the executable code, and then compile and link the code on your target machine.

If you think this is unhandy, you could ask Frank to provide some ready-to-compile archive of C++-only source code for download.

On a machine with the Java SDK

Using a machine with AFS access

On a machine with CMake, but not necessarily Java

On a machine without CMake and without Java

LCIO (last edited 2009-06-16 18:32:16 by localhost)