[postgis-devel] Public Raster C API

[Nathaniel Clay]

Remi,

There was some movement to move Postgis to CMake, but it stalled-out/failed
to get traction.

Thanks,

Nathaniel Hunter Clay

On Thu, May 28, 2015 at 4:17 AM, Rémi Cura <remi.cura at gmail.com> wrote:

> I'm afraid that if I use python (and not C) it is for a good reason !
> I'm really weak for the compilation stuff.
>
> When I have to, I painfully use CMake.
>
> Cheers,
> Rémi-C
>
> 2015-05-28 10:03 GMT+02:00 Nathaiel Clay <clay.nathaniel at gmail.com>:
>
>> Remi,
>>
>>
>>
>> Do have any experience with Autotools?  Right now I could use some help
>> with the process of extracting librtcore.so, eg. Moving it to dynamic
>> linking.
>>
>>
>>
>> *From:* postgis-devel-bounces at lists.osgeo.org [mailto:
>> postgis-devel-bounces at lists.osgeo.org] *On Behalf Of *Rémi Cura
>> *Sent:* Thursday, May 28, 2015 3:39 AM
>> *To:* PostGIS Development Discussion
>> *Subject:* Re: [postgis-devel] Public Raster C API
>>
>>
>>
>> Hey, I was looking recently for a python access to PostGIS raster from
>> within the base. A C api might be the first step? Cheers
>>
>> Le 28 mai 2015 09:04, "Nathaniel Clay" <clay.nathaniel at gmail.com> a
>> écrit :
>>
>> Bborie,
>>
>> Just to be clear we need to move from static linking to dynamic linking
>> and separate out "librtcore.so" from "rtpostgis.so". This can be done with
>> libtool,  honestly this would be my first attempt at using Autotools can I
>> get a little hand holding here.
>>
>> Humbly,
>>
>> Nathaniel Hunter Clay
>>
>>
>>
>> On Wed, May 27, 2015 at 8:10 PM, Bborie Park <dustymugs at gmail.com> wrote:
>>
>> Hm... Sounds like the Makefile needs changing to install librtcore.so.
>>
>>
>>
>> On Wed, May 27, 2015 at 4:22 PM, Nathaniel Clay <clay.nathaniel at gmail.com>
>> wrote:
>>
>> Bborie,
>>
>> I think it all gets rolled up into rtpostgis.so. As far as I can tell
>> there is no librtcore.so.
>>
>> Thanks,
>>
>> Nathaniel Hunter Clay
>>
>>
>>
>> On Wed, May 27, 2015 at 7:13 PM, Bborie Park <dustymugs at gmail.com> wrote:
>>
>> Nah. The library was meant to be consumed by whomever wants to consume
>> it. If the header is not copied, that'd be an oversight and a ticket should
>> be filed... Having said that I need to see where librtcore.so gets
>> installed...
>>
>>
>>
>> On Wed, May 27, 2015 at 2:41 PM, Nathaniel Clay <clay.nathaniel at gmail.com>
>> wrote:
>>
>> Bborie,
>>
>>
>>
>> The librtcore header is not copied, to /usr/include so I am assuming that
>> the library functions included in the library were meant to be private.
>> This is for a external project. Is this an over-site? Or am I missing
>> something fundamental.
>>
>>
>>
>> Thanks as Always,
>>
>>
>>
>> Nathaniel Hunter Clay
>>
>>
>>
>> On Wed, May 27, 2015 at 5:35 PM, Bborie Park <dustymugs at gmail.com> wrote:
>>
>> Actually, yes. raster2pgsql directly consumes librtcore...
>>
>>
>>
>> On Wed, May 27, 2015 at 2:33 PM, Bborie Park <dustymugs at gmail.com> wrote:
>>
>> Do you mean directly accessing librtcore? I believe you can go directly
>> at that library if so inclined.
>>
>>
>>
>> -bborie
>>
>>
>>
>> On Wed, May 27, 2015 at 2:31 PM, Nathaiel Clay <clay.nathaniel at gmail.com>
>> wrote:
>>
>> Hi All,
>>
>>
>>
>> Could we expose some of the raster C functions to read and write to
>> raster’s, and low level pixel to geo-point and geo-point to pixel and etc.
>> Just want your input, I am more than willing to do the work myself.
>>
>>
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Nathaniel Hunter Clay
>>
>>
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>
>>
>>
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>
>>
>>
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>
>>
>>
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>
>>
>>
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>
>>
>>
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20150528/883c67b4/attachment.html>