|
»
Windows builds
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
Windows builds
by Paragon Corporation-2
::
Rate this Message:
For the WKT Raster builds, I was thinking might make sense to keep them
separate instead of what I was originally thinking combining them since they run at different paces and also the wtraster binaries are small. How does the structure I have in place for postgresql 8.3 windows look. I have the WT Raster in a separate binary from the windows 1.4 etc. experimental. That way people who want to just pull the latest wkt raster windows binary for their current postgresql install can. WKT Raster folks, I have't played around with this yet so feel free to test to mae sure I compiled right, but I recall you saying their isn't a strict binding to PostGIS aside from it relies on PostGIS 1.4 and above? Just wondering if I have to specifically say which source I built against. Anyway the PostgreSQL 8.3 experimental binaries are here http://postgis.refractions.net/download/windows/pg83/experimental/ Thanks, Regina _______________________________________________ postgis-devel mailing list postgis-devel@... http://postgis.refractions.net/mailman/listinfo/postgis-devel |
|
|
Re: Windows builds
by Pierre Racine-2
::
Rate this Message:
Regina,
So if I understand well: There is one binary build of WKT Raster for PostgreSQL 8.3 under http://postgis.refractions.net/download/windows/pg83/experimental/ There is one binary build of WKT Raster for PostgreSQL 8.4 under http://postgis.refractions.net/download/windows/pg84/experimental/ The first one stand alone (or is the side PostGIS built specially for WKT Raster?) The second one goes with a special version of PostGIS (or is it the official build?) Normally there should be no special build of PostGIS for WKT Raster since WKT Raster should be independent and installable over most PostGIS versions. The first build structure would then be better as long as WKT Raster is not fully integrated with PostGIS (this seems far to me since, as you said, the development pace is very different). It is then important to make sure that WKT Raster is not dependent on any (AFAP) PostGIS build. We link with PostGIS for only one function. I haven't test much but I am pretty sure that the way WKT Raster is built right now makes it to work with PostGIS 1.3.5, 1.3.6 and 1.4. If not, then we will have to get rid of the link dependency (by implementing the only dependent function (st_raster_envelope() in PL/PGSQL)... We might rely on PostGIS 1.4 because of some building tools dependency but the code itself should not and it should run with most versions of PostGIS. Does this make sence? Pierre >-----Original Message----- >From: postgis-devel-bounces@... [mailto:postgis-devel- >bounces@...] On Behalf Of Paragon Corporation >Sent: 30 juin 2009 07:38 >To: 'PostGIS Development Discussion' >Subject: [postgis-devel] Windows builds > >For the WKT Raster builds, I was thinking might make sense to keep them >separate instead of what I was originally thinking combining them since they >run at different paces and also the wtraster binaries are small. > >How does the structure I have in place for postgresql 8.3 windows look. I >have the WT Raster in a separate binary from the windows 1.4 etc. >experimental. That way people who want to just pull the latest wkt raster >windows binary for their current postgresql install can. > >WKT Raster folks, > >I have't played around with this yet so feel free to test to mae sure I >compiled right, but I recall you saying their isn't a strict binding to >PostGIS aside from it relies on PostGIS 1.4 and above? > >Just wondering if I have to specifically say which source I built against. > >Anyway the PostgreSQL 8.3 experimental binaries are here >http://postgis.refractions.net/download/windows/pg83/experimental/ > > > >Thanks, >Regina > > > >_______________________________________________ >postgis-devel mailing list >postgis-devel@... >http://postgis.refractions.net/mailman/listinfo/postgis-devel postgis-devel mailing list postgis-devel@... http://postgis.refractions.net/mailman/listinfo/postgis-devel |
|
|
|
|
|
Re: Windows builds
by Mateusz Loskot-3
::
Rate this Message:
Pierre Racine wrote:
> We link with PostGIS for only one function. I can see at least 2. http://trac.osgeo.org/postgis/browser/spike/wktraster/rt_pg/rt_pg.h?rev=4009 > I haven't test much but I am > pretty sure that the way WKT Raster is built right now makes it to work > with PostGIS 1.3.5, 1.3.6 and 1.4. If not, then we will have to get rid > of the link dependency (by implementing the only dependent function > (st_raster_envelope() in PL/PGSQL)... I'm not sure it's feasible, because SQL layer of WKT Raster (rtpostgis.sql) heavily relies on PostGIS elements, just to mention the most important one - GEOMETRY type. How do you imagine to get independent of that? Best regards, -- Mateusz Loskot Senior Programmer, Cadcorp http://www.cadcorp.com _______________________________________________ postgis-devel mailing list postgis-devel@... http://postgis.refractions.net/mailman/listinfo/postgis-devel |
|
|
Re: Windows builds
by Pierre Racine-2
::
Rate this Message:
>I can see at least 2.
> >http://trac.osgeo.org/postgis/browser/spike/wktraster/rt_pg/rt_pg.h?rev =4009 There is st_raster_envelope(raster). What is the other? >> I haven't test much but I am >> pretty sure that the way WKT Raster is built right now makes it to work >> with PostGIS 1.3.5, 1.3.6 and 1.4. If not, then we will have to get rid >> of the link dependency (by implementing the only dependent function >> (st_raster_envelope() in PL/PGSQL)... > >I'm not sure it's feasible, because SQL layer of WKT Raster (rtpostgis.sql) >heavily relies on PostGIS elements, just to mention the >most important one - GEOMETRY type. > >How do you imagine to get independent of that? We can not be independent of PostGIS at the SQL level, but we can be independent of the dll versions if we do not link with it (as far as the SQL functions signatures do not change - they rarely do - and that they return the same objects). st_raster_envelope() can be implemented in plpgsql like I did for st_esriworldfile(raster) The constraints of having to install our own version of PostGIS would scary users too much. It is much better to stay away from the dll stuff and to rely on PostGIS only at the SQL level. Pierre _______________________________________________ postgis-devel mailing list postgis-devel@... http://postgis.refractions.net/mailman/listinfo/postgis-devel |
|
|
Re: Windows builds
by Mateusz Loskot-3
::
Rate this Message:
Paragon Corporation wrote:
> For the WKT Raster builds, I was thinking might make sense to keep them > separate instead of what I was originally thinking combining them since > they > run at different paces and also the wtraster binaries are small. > > How does the structure I have in place for postgresql 8.3 windows look. > I > have the WT Raster in a separate binary from the windows 1.4 etc. > experimental. That way people who want to just pull the latest wkt > raster > windows binary for their current postgresql install can. > > WKT Raster folks, > > I have't played around with this yet so feel free to test to mae sure I > compiled right, but I recall you saying their isn't a strict binding to > PostGIS aside from it relies on PostGIS 1.4 and above? > > Just wondering if I have to specifically say which source I built > against. > > Anyway the PostgreSQL 8.3 experimental binaries are here > http://postgis.refractions.net/download/windows/pg83/experimental/ Regina, I'd like to confirm that both, PostGIS 1.5 and WKT Raster binaries for PostgreSQL 8.4 work well for me. Now, I'm testing WKT Raster on Windows, and everything just works very well. I'd like to thank you, and all who are involved, very much for providing these experimental Windows binaries. WKT Raster is ready to let it out to the (brave) public :-) Best regards, -- Mateusz Loskot Senior Programmer, Cadcorp http://www.cadcorp.com **************************************************************************** This email is confidential and may be privileged and should not be used, read or copied by anyone who is not the original intended recipient. If you have received this email in error please inform the sender and delete it from your mailbox or any other storage mechanism. Unless specifically stated, nothing in this email constitutes an offer by Cadcorp and Cadcorp does not warrant that any information contained in this email is accurate. Cadcorp cannot accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of Cadcorp or one of its agents. Please rely on your own virus check. No responsibility is taken by Cadcorp for any damage arising out of any bug or virus infection. **************************************************************************** _______________________________________________ postgis-devel mailing list postgis-devel@... http://postgis.refractions.net/mailman/listinfo/postgis-devel |
| Free embeddable forum powered by Nabble | Forum Help |
