How to Get an Installation Kit - Firebird

The main page of the Firebird site usually displays a list of links to the latest releases for Linux and Windows. Other links will point you to distributions for other platforms. If a file has “src” in its name, it is buildable source code, not an installable kit.

Kit Contents

All of the kits contain all of the components needed to install the Firebird server:

  • The Firebird server executable
  • A number of other executables needed during installation and/or runtime
  • Shell scripts or batch files needed during installation, which may also be available as server utilities
  • The security database (isc4.gdb for v.1.0.x; security.fdb for v.1.5+)
  • One or more versions of the client library for installing on both the server and the client workstations
  • The command-line tools
  • The standard external function libraries and their declaration scripts (*.sql)
  • A sample database
  • The C header files (not needed by beginners!)
  • Text files containing up-to-the-minute notes for use during installation and configuration
  • Release notes and various README files (these are essential reading)

Kit Naming Conventions

File naming of kits across platforms is not consistent. Alas, it is not even “consistently inconsistent,” with builders often needing to conform to platform-specific conventions or simply making their own rules. However, certain elements in the file names will help you to identify the kit you want.

Classic or Superserver?

In general, the first part of the name string is “Firebird.”

  • If a Windows release supports the Classic server, it will be included in the same installer as the Superserver.
  • For POSIX platforms that support both architectures, separate installers are provided for the Classic server and Superserver. The kit name will begin with “FirebirdCS” (for Classic server) or “FirebirdSS” (for Superserver).
  • For minor platforms, the architecture might be less obvious and the first part of the name might be that of the OS or hardware platform.

Version Numbers

All release kit names should contain a dot-separated string of numbers in the following order: version number, release number, sub-release number. For example, “1.0.3” is the third sub-release of the initial (C code) release of Firebird version 1, while “1.5.0” is the initial sub-release of the release 5 (C++ code) of version 1. Most kits also include the absolute build number (e.g., or For some minor platforms, especially those that impose their own naming rules and build on different compilers, version numbers may be less obvious.

64-Bit I/O

For platforms that require a special build to support 64-bit I/O, you should look for the infix “64IO” somewhere in the name string. It will not be present in the names of kits for operating systems that provide 64-bit I/O support automatically, if it is available. Do not try to install a kit marked “64IO” on a version of that OS or hardware that does not support 64-bit I/O.

CPU Architecture

CPU architecture is usually included in the name string of the kit. For example, RPM installers for Linux generally include a chipset designator (e.g., i686). The showfiles display in the download list is generally a more useful indicator of the minimum chipset supported by the distribution. Assume Solaris kits are for Intel unless the “SPARC” tag is present in the kit name.

Mirror Sites

Once you find the required kit, click its hyperlinked file name. You will be directed to a list of mirror sites around the world, as shown in Figure.

SourceForge mirror site selector

SourceForge mirror site selector

It does not matter which mirror site you choose—the download kits are identical at all sites.

All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd Protection Status

Firebird Topics