Compile Windows version

In order to install the Windows package by recompiling the system, odaba-10.0.0.zip (or a higher version) may be downloaded from http://sourceforge.net/p/odaba . The package contains the complete documentation and the sources and procedures for rebuild the software. Besides, the package contains ODABA development databases for examining ODABA resources (source code, GUI resources).

After unpacking and copying the files to local directories, one may compile the system. In order to build the basic database libraries and tools, only the base sources need to be build. In order to build the GUI framework and ODABA GUI tools, QT 4.4 must have been installed.

ODABA can be installed on several MS Windows platforms (from Windows 2000/XP to Windows 7). In order to install ODABA, the following steps have to be performed

unpack the installation file
compile the source package with the required compiler
setup the ODABA folder

After installing the package successfully, one may create your own projects or load the ODABA databases in order to view ODABA resource details.

Unpack installation file

The installation is provided as simple .zip file, which can be unpacked easily by calling e.g.

unzip.exe odaba-11. x.x. zip

x.x stands for current subversion and release number. A folder with the name odaba-11. x.x will be created at the current location. After unpacking one may recompile the system with the required compiler.

Compiling MS Windows

After unpacking the installation file one may build the base libraries and tools (ODABA) as well as the GUI framework and GUI tools (ODABA GUI). Before, it is suggested to review the make file ( Makefile ). There is a more detailed guide in the file INSTALL that also lists the dependencies for common platforms by name.

In order to build ODABA, you need to call the following commands from a command line

.../vsvars32.bat (from your Visual Studio installation folder)

set QTDIR=qt_path (when installing GUI framework, only)

cd .../odaba-10. x.x ( x.x is current subversion and release number)

configure [--enable-gui] --prefix= target

make

A target location might be passed in order to create the ODABA system folder in a different place than in the Window's program folder (see next step: make install ). In order to build ODABA, only, without GUI framework one may call configure without parameters. In order to build the GUI framework, too, --enable-gui should be passed to the configure command. After build succeeded, binaries are stored in the bin folder of the installation folder.

When compiling with MS Visual Studio 7, you have to remove optimizations ( windows/Makefile.common :: C_CPP_FLAGS /O1 instead of /O2 ) for avoiding compiler bugs.

Prepare system folder

In order to copy resources to proper folders, one may call

make install

In order to get a proper working ODABA system folder (called ODABA here), make install has to be called or the the following resources have to be copied to the subsequent folder structure manually:

ODABA - binaries

ODABA\lib - libraries required for application development

ODABA\include - Interface header files (application development)

ODABA es - image files (icons, splash screens etc.)

ODABA\bat - command procedures for compiling (application development)

ODABA pl - template files for project initialization

The ODABA system folder requires compiler-specific run-time libraries.

msvcp NN [p].dll

msvcr NN [p].dll

mfc NN [p].dll

where NN is the version number (71,80,90,100) of the library in accordance with the compiler version. When these libraries are not available in the system path, it might become necessary to copy those to the system or ODABA path.

In order to run ODE applications, QT must be available (e.g. in the path) or the following QT libraries have to be copied to the ODABA system folder:

QtCore N .dll

QtGui N .dll

where N is the QT version number. When running a QT version compiled with a different compiler, one may also need run-time libraries corresponding to the QT compiler version.

In order to provide QT plug-ins e.g. for additional graphic formats, a qt.conf file has to be stored in the ODABA system folder:

[Paths]

Prefix= qt_path

Plugins= qt_path /plugins/

Now, one may test the installation by implementing the sample project ( Create the Sample project ).

to top Comment