[fdo-internals] S013-GB2: Build: Add PostGIS to build process

Greg Boone greg.boone at autodesk.com
Fri Oct 26 10:17:01 EDT 2007


Hi Mat,

On Linux, We could support the FDOPOSTGRESQL environment variable as
follows. Therefore, if it is set, the user can build from the installed
libraries. Is this what you are looking for?

---

INCLUDES = \
  -I../ \
  -I../../Inc  \
  -I../Message/Inc/  \
  -I../../../../Fdo/Unmanaged/Inc \
  -I../../../../Utilities/Common/Inc \
  -I$(FDOPOSTGRESQL)/include
  -I../../../../Thirdparty/pgsql/include

----

libPostGISProvider_la_LDFLAGS = \
  -shared \
  -release $(VERSION) \
  -L$(FDOPOSTGRESQL)/lib \
  -L../../../Thirdparty/pgsql/lib

---

Greg

-----Original Message-----
From: Mateusz Loskot [mailto:mateusz at loskot.net] 
Sent: Wednesday, October 24, 2007 6:21 PM
To: Greg Boone
Cc: Frank Warmerdam (External)
Subject: Re: [fdo-internals] S013-GB2: Build: Add PostGIS to build
process

Greg,

On my environment, I point to PostgreSQL location similarly as FDO does
it for MySQL, using environment variable FDOPOSTGRESQL.

Under Windows, default installation of PostgreSQL puts files under

C:\Program Files\PostgreSQL\X.Y\ where X.Y is version number like 8.2

So, I set FDOPOSTGRESQL=C:\Program Files\PostgreSQL\8.2

Then, it's enough to refer to include/lib locations as follows:

%FDOPOSTGRESQL%\include
%FDOPOSTGRESQL%\lib

I refer to or redefine FDOPOSTGRESQL in the PropertySheet:

http://trac.osgeo.org/fdo/browser/trunk/Providers/PostGIS/Src/PostGis.vs
props

(I've noticed it's been updated now)

I'd strongly recommend to not to build libpq from sources because it's
not a trivial process and may cause more problems than helps.

What do you think?

Regarding loading binaries, %FDOPOSTGRESQL%\bin should be added to the
PATH, that's all.

-- Mat


Greg Boone wrote:
> We can accommodate both options if required. The current setup is to
use
> the files in Thirdparty, with build scripts referencing Thirdparty
> locations only. If compilation from system files is required, then we
> would have to add these "Known" locations to the build scripts for
> PostGIS before the Thirdparty locations. I would prefer to avoid
adding
> new environment variables, so maybe it would be acceptable to
hard-code
> these. If not, the environment variables will have to be added to the
> build process.
> 
> Greg
> 
> -----Original Message-----
> From: Mateusz Loskot [mailto:mateusz at loskot.net] 
> Sent: Wednesday, October 24, 2007 5:48 PM
> To: Greg Boone
> Cc: Frank Warmerdam (External)
> Subject: Re: [fdo-internals] S013-GB2: Build: Add PostGIS to build
> process
> 
> Greg Boone wrote:
>> I dumped them all in. The server files are probably not necessary.
> 
> Greg,
> 
> One question, do we assume user will build his own version of libpq
> client library (using sources in Thirdpary dir) or will use binary
> already available on his system, probably installed using official
> PostgreSQL release packages?
> 
> 
> Cheers


-- 
Mateusz Loskot
http://mateusz.loskot.net



More information about the fdo-internals mailing list