From: npostavs@users.sourceforge.net
To: Mambo Levis <mambo.levis@gmail.com>
Cc: "ofv@wanadoo.es" <ofv@wanadoo.es>,
24574@debbugs.gnu.org, "a.s@realize.ch" <a.s@realize.ch>
Subject: bug#24574: emacs-module is not GPL compatible (Windows)
Date: Tue, 04 Oct 2016 22:48:41 -0400 [thread overview]
Message-ID: <8737kby0hi.fsf@users.sourceforge.net> (raw)
In-Reply-To: <732813402.3896868.1475423601606@mail.yahoo.com> (Mambo Levis's message of "Sun, 2 Oct 2016 15:53:21 +0000 (UTC)")
Mambo Levis <mambo.levis@gmail.com> writes:
> Please, notice that this time the plugin_is_GPL_compatible. The
> problem is now that the module can't be found when a sqlite3.dll
> symbol is used.
What was the difference between this time and the previous time?
>
> The only thing left to do was to put sqlite.dll in the emacs\bin
> folder and Voilà, now it works. In fact I had already added the path
> and used to sqlite3.dll in my emacs init file, but the location was
> wrong; after my emacs-modules collection.
So there is no bug after all? Should we just close this report, or is
there perhaps some guidance we should add to the documentation about how
to build modules on Windows?
next prev parent reply other threads:[~2016-10-05 2:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1261593588.2422705.1475266631400.ref@mail.yahoo.com>
2016-09-30 20:17 ` emacs-module is not GPL compatible (Windows) Mambo Levis
2016-10-01 1:14 ` Óscar Fuentes
2016-10-01 1:21 ` Óscar Fuentes
2016-10-01 4:37 ` bug#24574: " Robert Cochran
2016-10-01 7:53 ` Alain Schneble
2016-10-01 12:31 ` Mambo Levis
2016-10-01 15:40 ` bug#24574: " Eli Zaretskii
2016-10-01 20:28 ` Mambo Levis
2016-10-02 6:24 ` Eli Zaretskii
2016-10-02 15:53 ` Mambo Levis
2016-10-05 2:48 ` npostavs [this message]
2016-10-05 16:51 ` Mambo Levis
2021-10-23 2:47 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737kby0hi.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=24574@debbugs.gnu.org \
--cc=a.s@realize.ch \
--cc=mambo.levis@gmail.com \
--cc=ofv@wanadoo.es \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.