notmuch/bindings/Makefile.local, branch 0.31.2

emacs: Use makefile-gmake-mode in Makefile*s

2020-08-10T00:14:36Z

Use `makefile-gmake-mode' instead of `makefile-mode' because the former also highlights ifdef et al. while the latter does not. "./Makefile.global" and one "Makefile.local" failed to specify any major mode at all but doing so is necessary because Emacs does not automatically figure out that these are Makefiles (of any flavor).

build: optionally build python-cffi bindings

2019-12-03T12:12:30Z

Put the build product (and tests) in a well known location so that we can find them e.g. from the tests.

bindings: clean extra file created by ruby extension build system

2018-05-15T01:18:18Z

Noticed by dkg; this file seems to be created by building the debian package, and perhaps by other distro package builds.

build: Allow user to specify ruby executable

2018-05-11T00:01:06Z

This way, one can build for a different Ruby than $PATH/ruby (e. g. different versions, or Ruby in other paths). Signed-off-by: Thomas Schneider

fix out of tree build

2017-03-12T12:17:29Z

In addition to use ${srcdir} and deliver ${NOTMUCH_SRCDIR} where needed, source from ruby bindings had to be copied to the out-of-tree target directory -- if the source files in source directory were referenced in build and there were also built object files there, those could have been considered as target files (and then not found when attempting to create bindings/ruby/notmuch.so).

bindings: drop build time message on missing ruby dependency

2016-04-16T11:26:40Z

The usual make message on everything being up to date is: make: Nothing to be done for 'all'. However, since commit d038b9320949c79503fe4b76870aaabf279405ab Author: David Bremner Date: Mon Jun 1 09:08:59 2015 +0200 build: integrate building ruby bindings into notmuch build process if one doesn't have the ruby dependencies installed, the message has been: Missing dependency, skipping ruby bindings Restore the usual behaviour by dropping the message. It's redundant during build anyway, since the configure script already outputs: Checking for ruby development files... No (skipping ruby bindings)

build/ruby: use notmuch configure script values for shared lib

2015-06-14T06:23:55Z

This is supposed to help build on systems like MacOS with different conventions for naming shared libraries. We have already computed the relevant names, so doing it again in ruby seems like a bad idea.

lib, ruby: make use of -Wl,--no-undefined configurable

2015-06-13T15:52:48Z

In particular this is supposed to help build on systems (presumably using a non-gnu ld) where this flag is not available.

build: integrate building ruby bindings into notmuch build process

2015-06-12T07:12:28Z

Because ruby generates a Makefile, we have to use recursive make. Because mkmf.rb hardcodes the name Makefile, put our Makefile{.local} in the parent directory.