Drizzle - A Microkernel DBMS for High Performance Scale-Out Applications
Blog | Bugs | Build Farm | Events | Feature Requests | IRC | LCOV | Mailing List | Planet Drizzle | Source Code | Source Docs | Wiki

Contents 1 Overview 2 Build Tools 3 Resolving Package Dependencies 4 libdrizzle 4.1 Source Tarball 4.2 Launchpad 5 Getting the Code 6 Compiling the code 6.1 Configure flags and safety net 7 Next Steps

Overview

Drizzle is hosted at Launchpad and uses Bazaar for source code version control.

Build Tools

• If the bzr package is not available on your system you can download from https://launchpad.net/bzr
• Make sure you have autoconf, automake and libtool installed
• On Solaris you should build with Sun Studio compilers

Resolving Package Dependencies

Each operating system has its own list of dependencies. However, no matter what operating system you are on, you should install the following components most of which are available in package distributions for Linux and Solaris.

• bison
• boost
• chrpath
• doxygen
• gperf
• intltool
• libcurl4-gnutls
• libdrizzle
• libevent
• libgtest (source)
• libgnutls
• libreadline5 | libreadline
• libpcre3
• libboost-program-options (source)
• perl (>= 5.6.0)
• protobufs (>= 2.1.0)
• uuid
• zlib1g (>= 1:1.1.3-5)

Lenz Grimmer has created RPM packages of protobuf for Fedora, Mandriva, RHEL/CENTOS and OpenSUSE, available via his package repository on the openSUSE build service.

Resolving dependencies on CentOS 5

Resolving dependencies on FreeBSD 7.X

Resolving dependencies on Mac OS X

Resolving dependencies on Ubuntu

libdrizzle

libdrizzle is the client and protocol library that is required to build Drizzle. You can either grab a tarball release from the libdrizzle project page or you can grab the latest source from Launchpad.

Source Tarball

Grab the latest from the project page and install by replacing VERSION with the version you downloaded and running:

tar xvzf libdrizzle-VERSION.tar.gz
cd libdrizzle-VERSION
./configure
make
make install

NOTE: The config/autorun.sh step is not required when using source tarballs. On some platforms this may result in issues compiling, e.g. Bug #526518. Please report any issues found to help the development teams.

Launchpad

Once you have bzr installed, you first need to log into launchpad and then create a bzr repo directory (this is only needed once for all bzr related projects):

bzr launchpad-login my_lp_username

mkdir ~/bzrwork
bzr init-repo --2a  ~/bzrwork
cd ~/bzrwork

And then grab the libdrizzle source code, build, and install:

bzr branch lp:libdrizzle
cd libdrizzle
./config/autorun.sh
./configure
make
make install

Getting the Code

mkdir ~/bzrwork
bzr init-repo --2a ~/bzrwork
cd ~/bzrwork
bzr branch lp:drizzle

or grab the latest source tarball from Launchpad

NOTE: The first time you branch drizzle for a new system can take some time depending on your network connection (e.g. 10 minutes)

Compiling the code

Configure flags and safety net

If you want to make drizzle to a specific directory, use:

./configure --prefix=/some/deploy/dir

The above is highly recommended while Drizzle is still in alpha stage. You don't want to run sudo make install with code that can potentially break your system.

NOTE ./config/autorun.sh -- clears the autom4te cache and reconfigures make and config

cd drizzle
./config/autorun.sh  # (not needed if using source tarball)
./configure
make
make install

The recommended installation to test Drizzle is:

 ./configure --prefix=$HOME/usr/local/drizzle && make && make install
 cd $HOME/usr/local/drizzle

... and start the server as shown in starting drizzled

Next Steps

Starting drizzled

If you are a contributor to Drizzle, you may want to continue with Contributing Code

If you are a Drizzle user, you may want to continue with Using Drizzle.

Also see http://devzone.zend.com/article/4793 for a great article on getting started with Drizzle