Firebird Development: Database Engine

If you want to contribute to the Firebird Core Engine Project, there are several tools that you have to install and configure. The first program you need is an CVS client which allows you to check out the latest version of the Firebird sources (if you want to actively contribute please ask in the "firebird-devel" mailing list for code review and for CVS write access). Next you need the C compiler (GCC for *nix or VC >=5 for Windows). Please always refer to the platform-related documents distributed with Firebird sources (in build_docs subdirectory) for detailed and up-to-date information about the version of C compiler, additional tools and environment setup requied for sucessful compilation from sources on your platform.

The usual Firebird compilation process require running Firebird/InterBase on build machine. If you can't afford this prerequisite (for example, you're going to port Firebird to new platform), you also need the fresh Firebird bootkit. The bootkit contains preparsed C files that are used in place of those generated by an existing system. These "bootstrap" the build. The boot build kit should be available from our website, or you can ask for the fresh one in firebird-devel mailing list.

Environment setup

Here are the steps you need to perform before actually can check out, edit and compile the Firebird:

Download and install your favorite CVS utility. I recommend WinCVS. For Linux you don't need any client software because CVS support should be included in your distribution.

After you are done with the installations you have to start your CVS client and check-out the modul "interbase" or "Firebird2" from the Sourceforge CVS repository. Please refer to our CVS How To for detailed instructions.

Compiling the sources

NOTE: If you use CVS to checked out the source make a backup copy of the original source checkout. If you muck up the build and want to start again it is easiest to restore from this original backup file (This is due to a weakness in the way the current build process works).

Unix - Firebird 1
Now open the prompt (terminal window) and change to the folder where you checked out the "interbase" module. Configure the build system for DEV (debug) or PROD (production) build

$./Configure.sh DEV|PROD [system]

where "system" is one from AIX, AP, AX, DELTA, DG, EPSON, HP700, HP800, HP9.0, HP10, IMP, MU, SCO, SGI, SOLARIS, SUN4, UNIXWARE, AIX_PPC, LINUX, FREEBSD, NETBSD, DARWIN.

setup environment variables required for compilation

$source Configure_SetupEnv.sh

Build either CLASSIC or SUPER architectures.

$make firebird            -- for classic version 
# OR
$make super_firebird      -- for super version.

Windows - Firebird 1
Under construction...

Unix - Firebird 2
The Firebird 2 build process is built on Autoconf, so usual ./Configure, make, make install should work for you.

Windows - Firebird 2
Under construction...

Deploying the compiled files

Unix - Firebird 1
On any Unix based system, the usual make install should work for you. You can also use "classicrpmfile", "classictarfile", "superrpmfile", "supertarfile" or "clasicpackages" and "superpackages" make targets to build distributable packages (tar.gz, rpm or both) without actually installing compiled Firebird to your build machine.

Windows - Firebird 1
Under construction...

Unix - Firebird 2
The Firebird 2 build process is built on Autoconf, so usual make install should work for you.

Windows - Firebird 2
Under construction...

Contribute to the Firebird Core Engine Project

If you want to join the Firebird team you have to do next things:

Take your time to watch the traffic in "firebird-devel" mailing list for awhile until you will not get comfortable with our development efforts, structure, process and future plans.
Choose your working area:
- You can join one of our development drifts.
- You can choose a bug to fix it.
- You can propose and design a new feature. It's better to consult it in IB-Architect mailing list first.
Post in the "firebird-devel" mailing list about your intention, area of development and how you want to implement it.
Ask for code review for your patch.
If you have at least one patch accepted, and you want to continue your work on Firebird Core Engine, you can ask for CVS write access.

Coding standards and guidelines

Under construction...

Frequently Asked Questions

They will follow as soon as someone has asked something.

Additional informations and resources

If you have any suggestions or criticism please drop us an e-mail in "firebird-devel" mailing list.

Back to Core Engine Project.