rave is hosted by Hepforge, IPPP Durham
close Warning: Can't synchronize with repository "(default)" (/hepforge/svn/rave does not appear to be a Subversion repository.). Look in the Trac log for more information.

Version 14 (modified by anonymous, 18 years ago) (diff)

--

Rave Installation

Dependencies

The following software is needed to build rave:

  • (Gnu) C++ compiler
  • boost
  • clhep2 (should work with clhep1, also, though).

In the future, root's TMVA analysis toolkit can optionally be used by rave for flavor-tagging (along with non-TMVA dependent learning algorithms).

Linux/Unix?

Rave is fully autotooled. configure; make; make install are your friends. Package builders may want to call bootstrap before using configure and make.

Also note that various packages exist, see the download section.

Also check configure --help for special configuration options.

Java

In order to be able to build the java bindings, the following applications need to be installed on the system:

  • javac (gcj will soon be added as another option)
  • java
  • jar or fastjar
  • swig

If these are all found, then building the java bindings will be enabled per default. Disabling the bindings can also be specified explicitly: 

./configure --disable-java

It might be necessary to tell configure where to look for the java binaries and libraries: 

./configure --with-java-home=<JAVAHOME>

Note that with rave < 0.2.2, for java to work, it is necessary to turn off optimisation, e.g. 

configure CXXFLAGS="-g"

This is fixed in subversion head.

Cygwin

Your mileage under cygwin may vary :-( Please use the svn head, especially if you want the java bindings under cygwin. (Dont forget bootstrap, when building from the svn repository). Currently we've been able to compile a static version of rave only with a static version of clhep (compiled under cygwin, as well).

Install the following packages (incomplete list): boost, boost-devel, gcc-g++, gcc-java, gcc-mingw-java, pkg-config, swig, automake

This should be achievable without special tweaking and special configuration settings, though. The usual configure; make should do the job.

Using clhep libraries compiled with VC++ (the official way to build clhep under windows) has not yet been tried.

Our expertise in this area is likely to rise in the near future.

We might contribute patches to clhep2 to be able to build shared clhep2 libraries under cygwin.

Links: