Karoly Balogh
679f2f75b3
human68k: regenerated Makefiles
|
hai 1 ano | |
|---|---|---|
| .. | ||
| examples | hai 1 ano | |
| namespaced | %!s(int64=2) %!d(string=hai) anos | |
| src | %!s(int64=2) %!d(string=hai) anos | |
| Makefile | %!s(int64=2) %!d(string=hai) anos | |
| Makefile.fpc.fpcmake | %!s(int64=7) %!d(string=hai) anos | |
| README.txt | %!s(int64=16) %!d(string=hai) anos | |
| fpmake.pp | %!s(int64=2) %!d(string=hai) anos | |
| namespaces.lst | %!s(int64=2) %!d(string=hai) anos | |
README.txt
These units provides interface to Oracle Call Interface.
For the older 'oraoci' unit to compile you need oracle
server installed, these units was tested and performed
on Oracle 8.0.1.5 Standard server. One developer license
of Oracle server is free of charge...
Unit oraclew contains some procedures and functions,
which makes usage of oraoci not so painfull... But -
if you wanna to program in RAW OCI, you really can ;)
The oci and ocidyn units are a complete conversion from
Oracle's .h files. The former links statically to the
library, the latter dynamically.
You need to have oracle lib directory in ldpath, too,
or you can this path set in Makefile.fpc (is commented
there)
Joost van der Sluis,
[email protected]
For the older 'oraoci' unit to compile you need oracle
server installed, these units was tested and performed
on Oracle 8.0.1.5 Standard server. One developer license
of Oracle server is free of charge...
Unit oraclew contains some procedures and functions,
which makes usage of oraoci not so painfull... But -
if you wanna to program in RAW OCI, you really can ;)
The oci and ocidyn units are a complete conversion from
Oracle's .h files. The former links statically to the
library, the latter dynamically.
You need to have oracle lib directory in ldpath, too,
or you can this path set in Makefile.fpc (is commented
there)
Joost van der Sluis,
[email protected]