From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: Wrapping an Emacs dynamic module in a package Date: Mon, 17 Oct 2016 09:27:16 -0400 Message-ID: References: <83h98bzfo5.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1476711655 14577 195.159.176.226 (17 Oct 2016 13:40:55 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 17 Oct 2016 13:40:55 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Oct 17 15:40:51 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bw89U-0000WA-B7 for geh-help-gnu-emacs@m.gmane.org; Mon, 17 Oct 2016 15:40:28 +0200 Original-Received: from localhost ([::1]:33122 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bw89W-0007Fr-6n for geh-help-gnu-emacs@m.gmane.org; Mon, 17 Oct 2016 09:40:30 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39071) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bw7xY-00063e-Bj for help-gnu-emacs@gnu.org; Mon, 17 Oct 2016 09:28:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bw7xV-0004PE-8w for help-gnu-emacs@gnu.org; Mon, 17 Oct 2016 09:28:08 -0400 Original-Received: from [195.159.176.226] (port=33526 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1bw7xV-0004P2-1D for help-gnu-emacs@gnu.org; Mon, 17 Oct 2016 09:28:05 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1bw7x6-0003sp-3T for help-gnu-emacs@gnu.org; Mon, 17 Oct 2016 15:27:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 46 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:FigJsU1Bto1kB+t9ADjrTxZRgZc= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-Mailman-Approved-At: Mon, 17 Oct 2016 09:37:21 -0400 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:111551 Archived-At: > 1) I wrote an emacs module _mymod.so, as well as wrappers mymod.el (with > some local setup) and mymod-pkg.el (which only has a call to > define-package). FWIW, I doubt you wrote _mymod.so. Most likely you wrote something like _mymod.c and then you asked a C compiler and a linker turn that into a _mycmd.so. Yes, it's a nitpick, but when you send your bug-report, please try to use precise wording, because it's often surprisingly easy to introduce major confusion otherwise. > In my messages buffer, I see that Emacs tries to generate autoloads for the > .so, and fails with the error indicated in the original email ("_mymod.so:0:0: > error: scan-error: (Containing expression ends prematurely 238020 > 238021))"). In your bug-report, please show the corresponding backtrace. > 1) Should Emacs be able to generate autoloads for an .so? No. It shouldn't scan those files for autoloads. > 2) Does anybody have any experience with embedding an emacs module in an > emacs package? Any best practices I should be aware of? You might very well be the first to try it out. Note, tho, that the ELPA format is a tarball containing .el files, i.e. *source* files. Similarly, it should hold _mycmd.c rather than _mycmd.so. Then again, package.el doesn't know how to turn that _mycmd.c into _mycmd.so. You can probably work around that problem by adding something like (eval-when-compile (call-process "cc" nil nil nil )) in your mymod.el (so that when the .el file gets byte-compiled, it triggers compilation and linking of the C module). But yes, including the .so *should* happen work (barring bugs) as long as you're lucky enough to use the package on the right OS with the right Emacs version, on the right architecture. Stefan