From: Ralf Mattes <rm@seid-online.de>
To: "Germán Diago" <germandiago@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Guile status. Some questions to adopt usage as embedded game.
Date: Tue, 25 Mar 2014 18:14:48 +0100 [thread overview]
Message-ID: <20140325171448.GB865@seid-online.de> (raw)
In-Reply-To: <CAALp5N7at0Lgv5nE3CRt-JjidBHEzjRatGH_1pN+o2-Gc+VoJg@mail.gmail.com>
> > 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
next prev parent reply other threads:[~2014-03-25 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 11:27 Guile status. Some questions to adopt usage as embedded game Germán Diago
2014-03-25 16:26 ` Germán Diago
2014-03-25 17:14 ` Ralf Mattes [this message]
2014-03-25 20:50 ` Ludovic Courtès
2014-03-25 21:13 ` Ludovic Courtès
2014-03-26 13:56 ` Germán Diago
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140325171448.GB865@seid-online.de \
--to=rm@seid-online.de \
--cc=germandiago@gmail.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).