[geos-devel] Final thoughts on GEOS on iOS

[Malcolm Toon]

Sounds like we're just not going to be able to use GEOS.  That's fine.  We certainly have other options at our disposal, it would have just been nice to use GEOS with spatialite as it was intended.  I do appreciate the help, however I am a little surprised by the animosity of the group towards iOS development.  I would have thought a group that was dedicated to open development would have a little more of an open mindset.

Thanks again-
Malcolm


On Oct 12, 2013, at 3:00 PM, geos-devel-request at lists.osgeo.org wrote:

> Send geos-devel mailing list submissions to
> 	geos-devel at lists.osgeo.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.osgeo.org/mailman/listinfo/geos-devel
> or, via email, send a message with subject or body 'help' to
> 	geos-devel-request at lists.osgeo.org
> 
> You can reach the person managing the list at
> 	geos-devel-owner at lists.osgeo.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of geos-devel digest..."
> 
> 
> Today's Topics:
> 
>   1. GEOS Usage Follow Up (Malcolm Toon)
>   2. Re: GEOS Usage Follow Up (Frederik Ramm)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 11 Oct 2013 15:15:05 -0400
> From: Malcolm Toon <malcolm at foreflight.com>
> To: geos-devel at lists.osgeo.org
> Subject: [geos-devel] GEOS Usage Follow Up
> Message-ID: <98014FF3-7165-4221-A128-812DDBC6B290 at foreflight.com>
> Content-Type: text/plain; charset=windows-1252
> 
>> 
>> Message: 2
>> Date: Fri, 11 Oct 2013 15:51:45 +0200
>> From: Sandro Santilli <strk at keybit.net>
>> To: GEOS Development List <geos-devel at lists.osgeo.org>
>> Subject: Re: [geos-devel] GEOS Usage
>> Message-ID: <20131011135145.GT32424 at gnash>
>> Content-Type: text/plain; charset=us-ascii
>> 
>> On Fri, Oct 11, 2013 at 09:09:21AM -0400, Malcolm Toon wrote:
>>> Good morning!
>>> 
>>> We are evaluating spatialite with GEOS extensions for inclusion in an iOS project we're working on. Because we're targeting iOS, we cannot dynamically link the library in, so we'd have to statically link it in (unmodified though).  We've reviewed the license for GEOS and due to the LGPL and its static linking clause, it appears we'd have to provide the open source community access to any artifacts needed to build our project.  This isn't something we can do.  So, we're reaching out directly to see what advice you're giving other iOS developers in the same situation.  
>> 
>> Why can't you give access to the source code of your project ?
> 
> 
> 
> For the obvious reason? It's commercial, which we could use GEOS for on any other platform by dynamically linking it in, it's just on iOS we can't dynamically link.  Does anyone have any other thoughts about how this might be accomplished?  Does anyone know of an alternative license that GEOS might be distributed under?  We have no desire to change it without contributing the changes back, just want to be able to use it on a platform that doesn't provide dynamic linking.
> 
> Thank you!
> -Malcolm
> 
> ------------------------------
> 
> Message: 2
> Date: Fri, 11 Oct 2013 23:13:51 +0200
> From: Frederik Ramm <frederik at remote.org>
> To: geos-devel at lists.osgeo.org
> Subject: Re: [geos-devel] GEOS Usage Follow Up
> Message-ID: <52586A0F.5000900 at remote.org>
> Content-Type: text/plain; charset=windows-1252
> 
> Hi,
> 
> On 11.10.2013 21:15, Malcolm Toon wrote:
>> For the obvious reason? It's commercial, which we could use GEOS for
>> on any other platform by dynamically linking it in, it's just on iOS
>> we can't dynamically link.
> 
> Generally I have little sympathy here - you have chosen to use a
> proprietary operating system and you want to make money from selling a
> proprietary application, so just factor in the cost of re-inventing the
> wheel and hire a developer to do it for you.
> 
>> From the technical side, depending on what operations you need from GEOS
> and what the required bandwidth between GEOS and your application is, I
> could envisage a solution where you write a "GEOS daemon" that
> statically links to the library and is released openly, supporting a
> number of GEOS operations through simple network calls; and then you
> make your application talk to that daemon like it is discussed here
> http://stackoverflow.com/questions/7062388/how-can-i-make-my-ios-apps-talk-to-each-other
> or here
> http://stackoverflow.com/questions/8526694/does-ios-have-any-equivalents-to-dlls-ipc-process-spawning
> 
> Bye
> Frederik
> 
> -- 
> Frederik Ramm  ##  eMail frederik at remote.org  ##  N49?00'09" E008?23'33"
> 
> 
> ------------------------------
> 
> _______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geos-devel
> 
> End of geos-devel Digest, Vol 132, Issue 5
> ******************************************