Building Firebird Vulcan

Table of Contents

Windows 32 or 64
Building Firebird Vulcan on POSIX systems
Need help?

Windows 32 or 64

CVS Checkout
Setting up Your Build
Build!
Run Firebird Vulcan!

Anyone who would like to build Firebird Vulcan at home on a Windows system and has access to Visual Studio 7 can do so, reasonably easily, following this procedure.

CVS Checkout

Check out the sources from Sourceforge using the module name vulcan and any CVS client. The account is anonymous with no password. The CVSROOT is /cvsroot/firebird.

If you are using a version of CVS that does not check out empty directories, you'll need to create a Databases directory under src .

Setting up Your Build

Read the file README.vulcanWin32.txt in the top-level directory. It instructs you to

define vulcan as <vulcan root>\install
put %vulcan%\bin on your path before the paths to Firebird or InterBase
run the command file boot_copy.bat
copy or rename the file vulcan\builds\VisualStudio7\vulcan\vulcan.snl.template to vulcan\builds\VisualStudio7\vulcan\vulcan.sln

Then start Visual studio pointing it at the solution in vulcan\builds\VisualStudio7\vulcan
in the Visual Studio/Tools menu, pick Options/Projects, then Visual C++ files. If the list does not include <source root>/install/bin and <bison install directory>/bin , add them.

Build!

Click on build solution and it should churn happily for a while and eventually report that it built 26 projects with no failures.

The build automatically creates all the necessary databases, message files, dynamic header files, etc.

Run Firebird Vulcan!

Local connections will work immediately. To allow remote and loopback connections, start the server %vulcan%\bin\inetserver.exe with the switch -m.

The configuration files are deeply involved with the connection between a utility and a database. The best way to guess what the configuration files are doing to you is to run the fb_config utility with the -t option.

The fb_config utility traces back through the sequence of configuration files, then reports the translation of the database name, the name of the provider, and whether the provider was found.

C:\Harrison>config -t help.fdb
Opening c:\cygwin\home\vulcan\install/client.conf
Opening c:\cygwin\home\vulcan\install/databases.conf
Opening c:\cygwin\home\vulcan\install/master.conf
Looking up database name string "help.fdb"
 Matches "help.fdb",
 translates to "c:\cygwin\home\vulcan\install\help\help.fdb"
   Provider engine11
     Library "c:\cygwin\home\vulcan\install\bin\engine11":
     succeeded

C:\Harrison>isql help.fdb
Database:  help.fdb
SQL> show version;
ISQL Version: WI-V2.0.0.4027 Vulcan 1.0 Development
Firebird/x86/Windows NT (access method),
  version "WI-V2.0.0.4027 Vulcan 1.0 Development"
on disk structure version 11.0
SQL>