NonGNU-devel ELPA - jabber

OMEMO end-to-end encryption requires building a native C module. You need a C compiler, pkg-config, and libmbedtls (development headers).

If you installed from source (:vc or git clone), Emacs will offer to fetch the picomemo dependency and build the module on first load.

If you installed from ELPA, clone the repository and build manually:

git clone https://git.thanosapollo.org/emacs-jabber/
cd emacs-jabber
make module

Then copy the resulting jabber-omemo-core.so (or .dylib on macOS) into your ELPA package directory, which is already on load-path:

cp lisp/jabber-omemo-core.so ~/.emacs.d/elpa/jabber-VERSION/

The repository ships a guix.scm that builds straight from the current working tree, so you never need to update hashes or pin a commit. Whatever is checked out is what gets installed. Picomemo is fetched as a pinned input by guix.scm, so the optional OMEMO submodule does not need to be initialised.

git clone https://git.thanosapollo.org/emacs-jabber/
cd emacs-jabber

One-shot install into your user profile:

guix package -f guix.scm

A development shell with all build dependencies:

guix shell -D -f guix.scm

To use emacs-jabber from a Guix Home configuration, load the package definition and reference it from your services:

(use-modules (gnu home)
             (gnu home services)
             (gnu home services guix)
             (gnu services)
             (guix channels)
             (guix gexp))

(define emacs-jabber-git
  (load "/path/to/emacs-jabber/guix.scm"))

(home-environment
 (packages (list emacs-jabber-git)))

Re-run guix home reconfigure after pulling new commits and the package will be rebuilt from the updated checkout.