mu4e: use mu4e-config instead of mu4e-meta

All these changes to avoid:

,----
| mu4e/meson.build:92: WARNING: Source item '/home/djcb/Sources/mu/build/mu4e/mu4e-meta.el' cannot be converted to File object, because it is a generated file. This will become a hard error in the future
`----

This is because we want to byte-compile a file we just before generated using
configure_file. This does not seem like a crazy thing, but meson threatens with
breaking the build at some point in the future.

So instead, we decide _not_ to compile this (very boring) file. But, users may
still have an older mu4e-meta.elc lying around, leading to confusion.

So, let's rename that file and we're golden.
This commit is contained in:
Dirk-Jan C. Binnema
2022-05-29 01:09:53 +03:00
parent b1ff292bbb
commit cf0f72e4a4
9 changed files with 25 additions and 27 deletions

12
mu4e/mu4e-config.el.in Normal file
View File

@ -0,0 +1,12 @@
;; auto-generated
(defconst mu4e-mu-version "@VERSION@"
"Required mu binary version; mu4e's version must agree with this.")
(defconst mu4e-builddir "@abs_top_builddir@"
"Top-level build directory.")
(defconst mu4e-doc-dir "@MU_DOC_DIR@"
"Mu4e's data-dir.")
(provide 'mu4e-config)