[fdo-internals] OGR ProjConverter.h/.cpp

[Greg Boone]

Ok.  What I will do to try and make things easier is create a secondary
Release configuration that expects all the bells and whistles and have
the default Release configuration link against the minimum set. 

 

NOTE: The updated provider configuration will reference GDAL from its
relative location in Thirdparty

 

I would like to get a set of notes together that describes how to build
a fully fledged OGR provider will a full set of GDAL/OGR capabilities
and post these on the wiki. Can someone volunteer this information? I
will validate the steps and be responsible for the wiki content.

 

Greg

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: Friday, October 19, 2007 4:02 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] OGR ProjConverter.h/.cpp

 

Yes, that's the thing with OGR. One can compile it with a zillion
external libraries, which then imply that the provider has to link with
these also. I suggest you do a minimal configuration first, so link to a
basic OGR build, without OCI, PQ, etc... Then we can go from there.

 

I keep a special directory on my computer, where I have set up a full
tree of all of these components and basically that's the only place
where I can do a fully loaded OGR provider build. I would expect if
someone needs to support weirdo formats, they will have to do their own
provider build, that links against the correct OGR.

 

Traian

 

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Friday, October 19, 2007 3:56 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] OGR ProjConverter.h/.cpp

 

Ok, the questions keep coming...

 

The release build expects to find 

 

proj.lib 

geos.lib 

geos_c.obj 

libpq.lib

oci.lib 

 

So, if we want to incorporate the OGR provider into the top level Open
Source build process, do we expect that proj, geos, postgresql and
oracle client be installed and a version of GDAL be available that uses
them ?

 

Greg

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: Friday, October 19, 2007 3:43 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] OGR ProjConverter.h/.cpp

 

 

I do not do debug builds, so only the Release build is up to date. The
settings for Debug are wrong. This is mostly because with GDAL one can
only have a single build when using its regular build tools. If you try
to do a debug provider build that links to release OGR libraries, there
are lots of problems (link and/or runtime), so I did not pursue that
path.

 

 

Traian

 

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Friday, October 19, 2007 3:39 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] OGR ProjConverter.h/.cpp

 

For the OGR provider, the linker settings are different between the
Debug and Release configurations:

 

Additional dependencies

 

Release:

 

fdo.lib fdocommon.lib fdogeometry.lib ogr.lib cpl.lib ogrsf_frmts.lib
ogrsf_frmts_sup.lib proj.lib geos.lib libpq.lib wsock32.lib oci.lib
geos_c.obj xerces-c_2.lib

 

Debug:

 

fdo.lib fdocommon.lib fdogeometry.lib ogr.lib cpl.lib ogrsf_frmts.lib
ogrsf_frmts_sup.lib

 

Delay-Load DLLs

 

                Release:

 

                                oci.dll;fdo.dll;fdogeometry.dll

 

                Debug

 

                                ----

 

Can I get a clarification on the expected settings?

 

Greg

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: Friday, October 19, 2007 3:14 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] OGR ProjConverter.h/.cpp

 

I think that one is supposed to be optional, for specifying any
overridden coordinate systems. I don't have this file on my drive.

 

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Friday, October 19, 2007 3:12 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] OGR ProjConverter.h/.cpp

 

Is there also supposed to be a file:  projections.txt?

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: Friday, October 19, 2007 2:51 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] OGR ProjConverter.h/.cpp

 

That's mostly because I'm an idiot who can't use SVN. They should be
there now.

 

Traian

 

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Friday, October 19, 2007 2:49 PM
To: FDO Internals Mail List
Subject: [fdo-internals] OGR ProjConverter.h/.cpp

 

Hi All,

 

I am trying to build the OGR provider. The Windows solution requires
ProjConverter.h and ProjConverter.cpp. What are the source of these
files? They do not seem to be in the SVN.

 

Greg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20071019/a49d313e/attachment.html