liblo-devel Mailing List for LibLO

FYI that quote is from the other link:
http://code.google.com/p/vvopensource/

<Here's" rel="nofollow">http://code.google.com/p/vvopensource/>Here's another article I found
backing up what Sebastien says (it's much easier to read than the LGPL):

http://loufranco.com/blog/files/lgpl-and-the-iphone.html

I give up :)

On Fri, Jan 28, 2011 at 2:23 PM, Sebastien Bourdeauducq <
seb...@mi...> wrote:

> On Fri, 2011-01-28 at 12:32 -0800, Charlie Roberts wrote:
> > This page seems to sum up the situation:
> >
> >
> >
> http://huyzing.com/2009/08/24/compatibility-between-the-iphone-app-store-and-the-lgpl/
>
> "Recently it's been brought to my attention that the LGPL doesn't cover
> static libraries"
>
> This simply isn't true (see my previous post). See:
> http://www.gnu.org/copyleft/lesser.html
> section 4 "Combined Works" and paragraph d). The LGPL explicitly makes a
> distinction between static and shared libs.
>
> S.
>
>
>
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>

On Fri, 2011-01-28 at 12:32 -0800, Charlie Roberts wrote:
> This page seems to sum up the situation:
> 
> 
> http://huyzing.com/2009/08/24/compatibility-between-the-iphone-app-store-and-the-lgpl/

"Recently it's been brought to my attention that the LGPL doesn't cover
static libraries"

This simply isn't true (see my previous post). See:
http://www.gnu.org/copyleft/lesser.html
section 4 "Combined Works" and paragraph d). The LGPL explicitly makes a
distinction between static and shared libs.

S.

This page seems to sum up the situation:

http://huyzing.com/2009/08/24/compatibility-between-the-iphone-app-store-and-the-lgpl/

Here's an LGPL OSC library that grants the static exception the above
article mentions:

http://code.google.com/p/vvopensource/

Is there any interest in maintaining an LGPL license but adding an exception
for iPhones? A short blurb on the homepage would be enough. Otherwise I can
move to the above Obj-C library, but, I like liblo!

Thanks - Charlie

On Thu, Jan 27, 2011 at 12:08 PM, Philippe Mougin <pm...@ac...> wrote:

> Hi Charlie,
> You can use liblo on iPhone (I'm not aware of any restriction from Apple on
> LGPL stuff). Just build liblo as a static library and use it in your iPhone
> applications. It works.
> To comply with LGPL you'll need to provide the object code (e.g., your .o
> files) allowing people to relink your app with their own liblo versions if
> they want to.
>
> Philippe Mougin
> http://pmougin.wordpress.com
>
> Le 27 janv. 2011 à 18:44, Charlie Roberts a écrit :
>
> > Thanks for letting me know. And infinite thanks for everybody's work on
> liblo... I'm sad to have to leave it for a while. - Charlie
> >
> > On Thu, Jan 27, 2011 at 2:29 AM, Stephen Sinclair <rad...@gm...>
> wrote:
> > On Wed, Jan 26, 2011 at 11:30 PM, Charlie Roberts <big...@gm...>
> wrote:
> > > Hello all,
> > > I know that the license was only just changed to LGPL in the last
> release,
> > > but I'm wondering if there has been any thoughts about changing it
> (again)
> > > for use in mobile applications? You can't have dynamically linked
> libraries
> > > in the App Store, for example.
> > > Thanks for any info... - Charlie
> >
> > In general I'm not sure about the current status of
> > Apple-compatibility with any GPL-style license at all..
> > Since there exists other OSC libraries that are BSD licensed, I'm not
> > convinced it's worth worrying about.
> >
> > Steve
>
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>

Hi Charlie,
You can use liblo on iPhone (I'm not aware of any restriction from Apple on LGPL stuff). Just build liblo as a static library and use it in your iPhone applications. It works.
To comply with LGPL you'll need to provide the object code (e.g., your .o files) allowing people to relink your app with their own liblo versions if they want to. 

Philippe Mougin
http://pmougin.wordpress.com

Le 27 janv. 2011 à 18:44, Charlie Roberts a écrit :

> Thanks for letting me know. And infinite thanks for everybody's work on liblo... I'm sad to have to leave it for a while. - Charlie
> 
> On Thu, Jan 27, 2011 at 2:29 AM, Stephen Sinclair <rad...@gm...> wrote:
> On Wed, Jan 26, 2011 at 11:30 PM, Charlie Roberts <big...@gm...> wrote:
> > Hello all,
> > I know that the license was only just changed to LGPL in the last release,
> > but I'm wondering if there has been any thoughts about changing it (again)
> > for use in mobile applications? You can't have dynamically linked libraries
> > in the App Store, for example.
> > Thanks for any info... - Charlie
> 
> In general I'm not sure about the current status of
> Apple-compatibility with any GPL-style license at all..
> Since there exists other OSC libraries that are BSD licensed, I'm not
> convinced it's worth worrying about.
> 
> Steve

Thanks for letting me know. And infinite thanks for everybody's work on
liblo... I'm sad to have to leave it for a while. - Charlie

On Thu, Jan 27, 2011 at 2:29 AM, Stephen Sinclair <rad...@gm...>wrote:

> On Wed, Jan 26, 2011 at 11:30 PM, Charlie Roberts <big...@gm...>
> wrote:
> > Hello all,
> > I know that the license was only just changed to LGPL in the last
> release,
> > but I'm wondering if there has been any thoughts about changing it
> (again)
> > for use in mobile applications? You can't have dynamically linked
> libraries
> > in the App Store, for example.
> > Thanks for any info... - Charlie
>
> In general I'm not sure about the current status of
> Apple-compatibility with any GPL-style license at all..
> Since there exists other OSC libraries that are BSD licensed, I'm not
> convinced it's worth worrying about.
>
> Steve
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>

On Wed, Jan 26, 2011 at 11:30 PM, Charlie Roberts <big...@gm...> wrote:
> Hello all,
> I know that the license was only just changed to LGPL in the last release,
> but I'm wondering if there has been any thoughts about changing it (again)
> for use in mobile applications? You can't have dynamically linked libraries
> in the App Store, for example.
> Thanks for any info... - Charlie

In general I'm not sure about the current status of
Apple-compatibility with any GPL-style license at all..
Since there exists other OSC libraries that are BSD licensed, I'm not
convinced it's worth worrying about.

Steve

On Wed, 2011-01-26 at 14:30 -0800, Charlie Roberts wrote:
> I know that the license was only just changed to LGPL in the last
> release, but I'm wondering if there has been any thoughts about
> changing it (again) for use in mobile applications? You can't have
> dynamically linked libraries in the App Store, for example.

The LGPL does not apply to shared libraries only. If you use a LGPL
static library, it would mean that you should provide the necessary
files (e.g. object files) to re-link the executable against another
version of the library.

S.

Hello all,

I know that the license was only just changed to LGPL in the last release,
but I'm wondering if there has been any thoughts about changing it (again)
for use in mobile applications? You can't have dynamically linked libraries
in the App Store, for example.

Thanks for any info... - Charlie