LucidDbBuildFromSourceDistribution
From Eigenpedia
Building LucidDB from a source distribution is almost identical to building LucidDB from a Perforce sandbox.
First, obtain and unpack a source distribution of the Eigenbase platform; this includes the source code for LucidDB and all of its dependencies, including third-party libraries and build tools. You can get the latest release from the sourceforge.net download page for Eigenbase.
The archive will be named something like eigenbase-src-0.6.0.tar.bz2. Unpack it with this command:
tar xjf eigenbase-src-0.6.0.tar.bz2
When the tar command completes, you will have a directory like eigenbase-src-0.6.0. Underneath will be a luciddb subdirectory, plus a number of sibling subdirectories for the other Eigenbase and third-party components needed to build LucidDB.
Now, follow the instructions in LucidDbBuildFromPerforce, using eigenbase-src-0.6.0 where the instructions refer to dev.
If you're feeling either lucky or impatient, these are the fast-track steps for a full build on Linux:
- Make sure you have JDK 1.6 installed, with JAVA_HOME environment variable set
- Make sure you have at least g++ 4.1.x installed (note that very recent g++ versions such as 4.3.2 may have problems)
- Make sure you have cmake 2.6.0 or later available
- If you are building on a machine which supports both 32-bit and 64-bit builds, follow the instructions from Fennel64Bit#Build Machine Setup Notes.
- cd dev/farrago
- Only necessary before release 0.9.2: echo 'release.gpl=true' > customBuild.properties
- cd ../luciddb
- ./initBuild.sh --with-optimization --without-debug
This may actually work for you, but if you encounter errors, you'll need to go step-by-step through the full instructions. And even if it works, you should still read through those instructions to familiarize yourself with what's going on. In particular, you must follow the steps for setting up the correct environment variables for running executables after the build completes.
For builds intended for production use, be sure to specify --with-optimization --without-debug to initBuild.sh.
If you want your build to exactly match the official release builds, then for the optional customBuild.properties step above, add the line build.mode=release to that file. This will prevent certain developer-related features such as LucidDB's test harness from being added to the release image. In general, you probably don't need to worry about this.
See the Perforce instructions link above for what to do with your build after it completes successfully.

