Karoly Balogh 679f2f75b3 human68k: regenerated Makefiles 1 vuosi sitten
..
examples 679f2f75b3 human68k: regenerated Makefiles 1 vuosi sitten
namespaced 91318fdea2 * Dotted filenames for package ibase 2 vuotta sitten
scripts d493d44d6d * Package ibase moved + makefile.fpc's. fpmake and regenned makefiles 17 vuotta sitten
src 9197def8cc * Attempt to load .so.2. Fixes issue #40495 1 vuosi sitten
Makefile 2289c1f6a2 * Remove redundant Makefile.fpc 2 vuotta sitten
Makefile.fpc.fpcmake 98f00acb06 * trunk to 3.3.1 7 vuotta sitten
README.txt 4bf254bc32 * added .txt extensions to all README, TODO and COPYING files 16 vuotta sitten
fpmake.pp bd4e9676fa * Add namespaces.lst 2 vuotta sitten
namespaces.lst 91318fdea2 * Dotted filenames for package ibase 2 vuotta sitten

README.txt

This is the README file for the INTERBASE package of FPC

How to compile
--------------

You can compile by hand, or use the makefile. The makefile uses the
makefile.fpc that is distributed by the FPC team.

1) Using the makefile.
Edit the makefile:
set the DEFAULTFPCDIR
if libgds is not in /usr/lib, set GDSLIBDIR
type 'make'. It should all compiler

2) By hand:
simply type:
ppc386 -S2 ibase60
(or ibase40 if you have the older version)

If your libgds.so file is not in /usr/lib, you may need to add
-Fl/path/to/libgds

Using the testprogram
---------------------

The mkdb script (mkdb.pas batch file) creates a database.
default testdb.gdb is assumed. You can override that by
specifying an alternate database as an option.

The testib program connects to the testdatabase. You must edit
the testib.pp file and set the database, password and username.
After editing, compile the program.
Run it and it will display the contents of the database.

Enjoy !

Michael.