[postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?

[Obe, Regina]

Pierre,

Welcome to the "Those who've successfully compiled under Windows club".
Here is your proverbial purple heart.

We are a very elite group.  Linux people have way too easy of a time.
They are not worthy of being in our club.

  Now we just have to get Paul's nifty gui compiled.  Have you ventured
there yet?  I haven't had time to yet.

For the instructions -- you could just put it on your site and link from
PostGIS wiki for now, but yes I agree we need a better wiki.

Speaking of documentation -- would be nice if we had Doxygen or
something similar for the developer documentation.  I think it would
make it a bit easier to navigate.  I guess we can talk about that at the
sprint too and I think someone has mentioned that before.

Thanks,
Regina


-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of
Pierre Racine
Sent: Wednesday, March 04, 2009 9:56 AM
To: PostGIS Development Discussion
Subject: RE:
[postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?

He!

I'm happy to say that today, march 4th 2009, I have a PostgreSQL/PostGIS
compiled by myself running on Windows XP! Today is a nice day! (Not like
yestesday :-()

I can now give a try at compiling WKT Raster.

Please never, ho never say again on this mailing list that:

1) You don't have to compile PostgreSQL. You DO have to compile
PostgreSQL in order to compile PostGIS. PostGIS makefiles are highly
dependent on lots of stuff PostgreSQL makes when building that are not
provided in the PostgreSQL installation. Luckily we don't have to
compile Linux to compile PostgreSQL... And to compile ArcGIS to compile
our own ArcGIS Python script...

2) That it takes 20 minutes. The setup is very different on Windows. All
this is a Linux thing and you have to do a lot trial and error to get it
to work on Windows. Took me three days (and two nights).

I promess I will write a compilation procedure if I can convince PostGIS
people to migrate the PostGIS wiki from a 90's wiki to a new millenium
wiki.

Pierre

>-----Original Message-----
>From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-
>bounces at postgis.refractions.net] On Behalf Of Pierre Racine
>Sent: 3 mars 2009 15:58
>To: PostGIS Development Discussion
>Subject: RE: [postgis-devel]
WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
>
>Even though proj-4.6.1 was built without problem, make install did not
>copy it in the /usr tree. Is there a way to see the order in wich it
>looks for dll and load them so I could identify what's missing?
>
>>-----Original Message-----
>>From: postgis-devel-bounces at postgis.refractions.net
>[mailto:postgis-devel-
>>bounces at postgis.refractions.net] On Behalf Of Pierre Racine
>>Sent: 3 mars 2009 15:02
>>To: PostGIS Development Discussion
>>Subject: RE: [postgis-devel] WKT
>Raster:WhyhavingtocompilePostgreSQL&PostGISfirst?
>>
>>>> So I could build everything but now when I try to execute
>postgis.sql
>>in
>>>> a database I get:
>>>
>>>> ERROR:  could not load library
>>>> "C:/msys/1.0/local/pgsql/lib/postgis-1.4.dll": unknown error 126
>>>>
>>>> Any idea?
>>>>
>>>> I compiled postgresql-8.3.6, postgis-svn, geos\trunk and proj-4.6.1
>>>
>>>You also need to install postgis, not only build it.
>>
>>It's done and there. I'm wondering if it just can't find proj4. Is is
a
>>dll or only a link library.
>>_______________________________________________
>>postgis-devel mailing list
>>postgis-devel at postgis.refractions.net
>>http://postgis.refractions.net/mailman/listinfo/postgis-devel
>_______________________________________________
>postgis-devel mailing list
>postgis-devel at postgis.refractions.net
>http://postgis.refractions.net/mailman/listinfo/postgis-devel
_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.