LucidDbBuildFromPerforce
Contents |
LucidDB build is based on Farrago build
To build LucidDB from Perforce, follow the FarragoBuild but with the modifications noted in the sections below.
Perforce client view
When mapping your Perforce client view, add lines for luciddb and extensions:
//open/dev/thirdparty/... //YOURCLIENT/dev/thirdparty/...
//open/dev/fennel/... //YOURCLIENT/dev/fennel/...
//open/dev/farrago/... //YOURCLIENT/dev/farrago/...
//open/dev/luciddb/... //YOURCLIENT/dev/luciddb/...
//open/dev/extensions/... //YOURCLIENT/dev/extensions/...
If you would prefer to pull via Git or Subversion, see access instructions in PerforceToGitOrSubversionReplication.
Running initBuild.sh
Instead of running initBuild.sh from dev/farrago, run it from dev/luciddb instead. Also, there's no need to specify the --with-fennel parameter (this is the default for LucidDB builds).
See LucidDbBuildFromSourceDistribution for some fast-track setup steps here.
Running programs
Instead of running programs and commands from dev/farrago, run them from dev/luciddb. The LucidDB build supports the following programs and commands:
- sqllineEngine: as for Farrago, but sets the LucidDB personality
- lucidDbServer: similar to farragoServer, but sets the LucidDB personality
- sqllineClient: as for Farrago, but connects using the LucidDB JDBC driver
- ant createCatalog: recreates the LucidDB catalog (which is stored separately from the Farrago catalog)
- ant backupCatalog: backs up the LucidDB catalog
- ant restoreCatalog: restores the LucidDB catalog
- ant test: run LucidDB checkin acceptance tests
- ant createEclipseProject: creates an Eclipse project for use in developing LucidDB code
Alternatively, instead of running directly in the development sandbox (dev/luciddb), you can also install your new LucidDB build as a user would do (look in the dev/luciddb/dist directory for the tarball).
Tracing
LucidDB tracing is similar to Farrago's; settings are controlled by editing dev/luciddb/trace/LucidDbTrace.properties, and output goes to LucidDbTrace.log in the same directory.
Debugging
For Java, see FarragoEclipse. For C++, see FarragoFennelDebugging.
