unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex <agrambot@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: eggert@cs.ucla.edu, 34849@debbugs.gnu.org
Subject: bug#34849: Compilation issues with g++ on some files
Date: Mon, 18 Mar 2019 22:45:40 -0600	[thread overview]
Message-ID: <875zsfmpzf.fsf@gmail.com> (raw)
In-Reply-To: <E1h64QM-0000T6-Fn@fencepost.gnu.org> (Richard Stallman's message of "Mon, 18 Mar 2019 22:24:18 -0400")

Richard Stallman <rms@gnu.org> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > I'm thinking about trying my hand at making a Qt [1] GUI for Emacs,
>   > which is unfortunately written in C++.
>
> There are two problems with that.
>
> 1. I don't want C++ code in the Emacs distribution.  This isn't the sort
> of crucial thing that would override that general policy.

For the record, the addition of C++ was about as minimally invasive as
the Objective C code is, but I understand your desire to keep C++ out.

> 2. Qt is licensed under GPL 3 only.  If we ever need to make a GPL
> version 4, we would release the next Emacs version under GPL 4-or-later,
> so it could not be linked with Qt.
>
> You can make the changes you wish, but we should not include it in
> Emacs itself.

The licensing situation is unfortunate. Thank you for giving me notice
of this before spending much time on making it work.





  parent reply	other threads:[~2019-03-19  4:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 21:12 bug#34849: Compilation issues with g++ on some files Alex
2019-03-17  5:22 ` Alex
2019-03-18  1:47   ` Richard Stallman
2019-03-18 16:18     ` Alex
2019-03-19  2:24       ` Richard Stallman
2019-03-19  2:37         ` Paul Eggert
2019-03-19  4:45         ` Alex [this message]
2019-03-19  7:33         ` Eli Zaretskii
2019-03-20  2:12           ` Paul Eggert
2019-03-20  6:04             ` Alex
2019-03-20  7:05               ` Eli Zaretskii
2019-03-20  6:38             ` Eli Zaretskii
2019-03-20  2:31           ` Richard Stallman
2019-03-20  6:53             ` Eli Zaretskii
2019-03-21  2:09               ` Richard Stallman
2019-03-20  2:32           ` Richard Stallman
2019-03-20 10:53             ` Dmitry Gutov
2019-03-21  2:10               ` Richard Stallman

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875zsfmpzf.fsf@gmail.com \
    --to=agrambot@gmail.com \
    --cc=34849@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=rms@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).