Difference between revisions of "Building FRANKLIN on CentOS 5"

(Getting the source)
Line 3: Line 3:
== Introduction ==
== Introduction ==
Building Zimbra on any platform is really complex: there are many variables and places where things can go wrong.
This HOWTO covers the basic steps required to build Zimbra. For more information, see these documents/pages:
* [[http://varlogmessages.vroomvroom.org/documentation/solaris-port/build-instructions|Building Zimbra on Solaris]]
== Getting the source ==
== Getting the source ==

Revision as of 14:17, 1 December 2008


This HOWTO covers the basic steps required to build Zimbra. For more information, see these documents/pages:

Getting the source

There are two main ways to getting the Zimbra sources:

To download official Zimbra sources, first get proprietary Perforce client (free) from http://www.perforce.com/perforce/downloads/platform.html. Next create a temporary directory for the sources

$ mkdir /home/username/temp

Next do some linking to work around p4's default behaviour:

$ ln -s /home/username/temp /home/public

Then export some P4-related environment variables and do a full resync. This is required, because p4 is a proprietary program and it can't track changes for the public account.

$ export P4EDITOR=nano
$ export P4PORT=codes.zimbra.com:2666
$ p4 -u public -P public1234 -c public-view sync -f //depot/zcs/FRANKLIN/...

Perforce should now start downloading the source code.

Preparing the build environment

Stock CentOS5 install has only a few basic repositories configured. You should definitely add rpmforge to your list of repositories. You get the repository information and instructions from http://dag.wieers.com/rpm/packages/rpmforge-release.


Zimbra build problems can be divided into a couple main categories:

  • Undocumented, missing dependencies
  • Faulty assumptions about the build environment
  • Problems with the sources or the downloaded source tree

Instead of trying to document every problem I encountered, I'll simply describe how these problems can be circumvented.

Finding and installing missing dependencies

It's certain that Zimbra won't build cleanly if you just follow the various Wiki articles and README files. When the build fails, it's usually due to a missing dependency. If the error message tells you which software package is missing, you can find and install it pretty easily:

$ yum search package
$ yum install package

Most likely you need lots of development packages

repoquery -a -f *ldap.h

Verified Against: unknown Date Created: 4/28/2008
Article ID: https://wiki.zimbra.com/index.php?title=Building_FRANKLIN_on_CentOS_5 Date Modified: 2008-12-01

Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »

Jump to: navigation, search