Cannot change lispdir #320

Closed
uu1101 opened this Issue Nov 27, 2013 · 0 comments

Comments

Projects
None yet
1 participant
Contributor

uu1101 commented Nov 27, 2013

When building mu on Ubuntu, I would like to set the lispdir to the emacs24 specific directory:

./configure --with-lispdir='${prefix}/share/emacs24/site-lisp/mu4e/' ...

But the build system insists on installing mu4e on ${prefix}/emacs24/site-lisp/mu4e/

I think the issue is related to the following line:
https://github.com/djcb/mu/blob/master/mu4e/Makefile.am#L24

The GNU Coding Standards recommend instead:

If you are using Autoconf, write the default as ‘@lispdir@’. In order to make ‘@lispdir@’ work, you need the following lines in your configure.ac file:

lispdir='${datarootdir}/emacs/site-lisp'
AC_SUBST(lispdir)

Removing the line from Makefile.am allows configuring the lispdir.

Can the line be removed to make it easier to configure the installation directory of mu4e?

@uu1101 uu1101 pushed a commit to uu1101/mu that referenced this issue Dec 1, 2013

@medranocalvo medranocalvo * mu4e/Makefile: allow configuring the lispdir
`lispdir` is no longer hardcoded in the Makefile.

Users can set the desired `lispdir` at configure time, with `./configure
--with-lispdir='...'`; or at install time with `make lispdir='...' install`.

The default install path is the folder `mu4e/` inside whatever AM_PATH_LISP
finds, which is probably what the original default intended.

This change fixes #320.
b5e0e81

@uu1101 uu1101 added a commit to uu1101/mu that referenced this issue Dec 1, 2013

@uu1101 uu1101 * mu4e/Makefile: allow configuring the lispdir
`lispdir` is no longer hardcoded in the Makefile.

Users can set the desired `lispdir` at configure time, with `./configure
--with-lispdir='...'`; or at install time with `make lispdir='...' install`.

The default install path is the folder `mu4e/` inside whatever AM_PATH_LISP
finds, which is probably what the original default intended.

This change fixes #320.
44cc0bd

djcb closed this in #323 Dec 1, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment