+ harbour/contrib/gtwvg/make_gcc.sh
+ harbour/contrib/hbapollo/make_gcc.sh
+ harbour/contrib/hbclipsm/make_gcc.sh
+ harbour/contrib/hbct/make_gcc.sh
+ harbour/contrib/hbfbird/make_gcc.sh
+ harbour/contrib/hbfimage/make_gcc.sh
+ harbour/contrib/hbgd/make_gcc.sh
+ harbour/contrib/hbgt/make_gcc.sh
+ harbour/contrib/hbmisc/make_gcc.sh
+ harbour/contrib/hbmsql/make_gcc.sh
+ harbour/contrib/hbmysql/make_gcc.sh
+ harbour/contrib/hbnf/make_gcc.sh
+ harbour/contrib/hbodbc/make_gcc.sh
+ harbour/contrib/hbole/make_gcc.sh
+ harbour/contrib/hbpgsql/make_gcc.sh
+ harbour/contrib/hbtip/make_gcc.sh
+ harbour/contrib/hbtpathy/make_gcc.sh
+ harbour/contrib/hbw32/make_gcc.sh
+ harbour/contrib/hbw32ddr/make_gcc.sh
+ harbour/contrib/hbwhat32/make_gcc.sh
+ harbour/contrib/hbziparch/make_gcc.sh
+ harbour/contrib/hbzlib/make_gcc.sh
+ harbour/contrib/rddads/make_gcc.sh
+ harbour/contrib/xhb/make_gcc.sh
+ Added missing files to allow compilation using non standard
build system. Please note that some contribs require external
packages, so to succesfuully compile them you will have to
set a proper environment variable, pointing to a list of
directories, containig required package header files. Those
envvars are listed below :
APOLLO_INC
FIREBIRD_INC
FREEIMAGE_INC
GD_INC
MYSQL_INC
PGSQL_INC
ZLIB_INC
ADS_INC
Note that those envvars may contain list of directories,
for example :
export ADS_INC="/usr/include include ."
Also note that on Windows systems, using MingW or Cygwin, you will
have to generate a proper import files from dlls, available in those
packages - using MingW or Cygwin dlltool - to build end user programs,
utilizing those packages.
* harbour/contrib/mtpl_gcc.mak
* harbour/contrib/mtpl_gcc.sh
* harbour/contrib/make_gcc_all.sh
+ Added the rest of contrib libs to compile
* harbour/contrib/hbtpathy/tplinux.c
* harbour/contrib/hbtpathy/tpos2.c
* harbour/contrib/hbtpathy/tpwin32.c
+ Added an operating system guard around the content of
thses files to allow including all three files in a
library.
/* * $Id$ */ README 23/12/2003 - Harbour Low Level api for Postgres RDBMS It's to be seem like Harbour TMysql routines. IMPORTANT --------- The class TPostgres, only works with versions 7.4.x or greater, because some methods use information_schema and New PQexecParams, which use protocol 3.0 and this protocol is only compatible with 7.4 versions. BORLAND BCC ----------- Using this library with bcc, you will need import library, ex: implib libpq.lib libpq.dll or (advice this) build your own Postgres Library. Go to postgres directory \postgresql-7.4.5\src\interfaces\libpq Edit bcc32.mak and change the default borland directory for your needs. Example: BCB=c:\Borland\Bcc55 change postgresql-7.4.5\src\include\pg_config.h.win32 to pg_config.h after this make -f bcc32.mak Now look at \postgresql-7.4.5\src\interfaces\libpq\Release, you will find the all .libs and .dlls If want use the dll, link in your aplication blibpqdll.lib and send blibpq.dll together with your aplication If you don't wanna use .dll link blibpq.lib, that's it. LINUX GCC ---------- On Linux you will need link libpq or references by pq. For full api documentation look at: http://www.postgresql.org/docs/current/static/libpq.html FILES: postgres.c - Low level api tpostgre.prg - Class implementation, it's to be seems like TMysql. tests\simple.prg - Simple test class tests\stress.prg - Stress test tests\cache.prg - Show hot to use .dbf as pg cache, like TDataset for Delphi. TODO: That's all folks and sorry my poor english Rodrigo Moreno - rodrigo_moreno@yahoo.com