fpc/packages/ibase
tom_at_work 9428c78d63 Pass OPT to compilation of fpmake.
Solves issues with systems that e.g. require special options for compilation of programs (e.g. libc programs to find libc startup code) or the actual build has been compiled with options that are incompatible with default ones.

Tested changes by building an i386-linux local build and i386-linux->arm-linux cross-builds

git-svn-id: trunk@22397 -
2012-09-15 23:41:44 +00:00
..
examples + Regenerate all Makefiles's after adding x86_64 netbsd target 2012-04-24 23:15:18 +00:00
scripts
src * Patch from Ludo Brands to fix compilation under Windows (Bug 22691) 2012-08-22 11:35:24 +00:00
fpmake.pp * Set for which targets these packages have to be compiled for 2012-01-29 10:41:02 +00:00
Makefile Pass OPT to compilation of fpmake. 2012-09-15 23:41:44 +00:00
Makefile.fpc Pass OPT to compilation of fpmake. 2012-09-15 23:41:44 +00:00
Makefile.fpc.fpcmake
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.