[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Guile status. Some questions to adopt usage as embedded game.
From: |
Ralf Mattes |
Subject: |
Re: Guile status. Some questions to adopt usage as embedded game. |
Date: |
Tue, 25 Mar 2014 18:14:48 +0100 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
> > I am a (mainly) c++ advanced user with a strong background in linux,
> > writing a game that will run on iOS and Android as the main platforms.
> >
[ won't comment on the trechnical questions ... ]
> > 6.- Is there any incompatibility in using guile in a closed-source
> > project, regarding to the license?
It will be a nightmare on iOS. While Android allows dynamic linking of libraries
(so you only need to provide the source code of guile to your customers) Apple's
AppStore forbids any dynamic linking. So, in order to fulfill the requirements
of
Guile's LGPL you need to either distribute the source code of your application
as well
or at least distribute your application's object code (*.o and *.a files) so
your
customers can relink against a changed static version of libguile. But since
Apple
only allows signed code and the relinking will break this signing the relinked
application
won't run on a non-rooted device ... And since you seem to compile C++ code
relinking
will rely on the compiler's C++ ABI.
HTH Ralf Mattes