notmuch/bindings/Makefile.local

# -*- makefile -*-

dir := bindings

# force the shared library to be built
ruby-bindings: lib/$(LINKER_NAME)
ifeq ($(HAVE_RUBY_DEV),1)
	cd $(dir)/ruby && \
		EXTRA_LDFLAGS="$(NO_UNDEFINED_LDFLAGS)" \
		LIBNOTMUCH="../../lib/$(LINKER_NAME)" \
		NOTMUCH_SRCDIR='$(NOTMUCH_SRCDIR)' \
		$(RUBY) extconf.rb --vendor
	$(MAKE) -C $(dir)/ruby
endif

CLEAN += $(patsubst %,$(dir)/ruby/%, \
	.RUBYARCHDIR.time \
	Makefile database.o directory.o filenames.o\
	init.o message.o messages.o mkmf.log notmuch.so query.o \
	status.o tags.o thread.o threads.o)
build: integrate building ruby bindings into notmuch build process 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. 2015-06-01 09:08:59 +02:00			`# -- makefile --`

			`dir := bindings`

			`# force the shared library to be built`
build/ruby: use notmuch configure script values for shared lib 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. 2015-06-01 09:09:01 +02:00			`ruby-bindings: lib/$(LINKER_NAME)`
build: integrate building ruby bindings into notmuch build process 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. 2015-06-01 09:08:59 +02:00			`ifeq ($(HAVE_RUBY_DEV),1)`
lib, ruby: make use of -Wl,--no-undefined configurable In particular this is supposed to help build on systems (presumably using a non-gnu ld) where this flag is not available. 2015-06-01 09:09:00 +02:00			`cd $(dir)/ruby && \`
			`EXTRA_LDFLAGS="$(NO_UNDEFINED_LDFLAGS)" \`
build/ruby: use notmuch configure script values for shared lib 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. 2015-06-01 09:09:01 +02:00			`LIBNOTMUCH="../../lib/$(LINKER_NAME)" \`
fix out of tree build 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). 2017-03-12 12:59:13 +01:00			`NOTMUCH_SRCDIR='$(NOTMUCH_SRCDIR)' \`
build: Allow user to specify ruby executable 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 <qsx@chaotikum.eu> 2018-05-09 14:38:48 +02:00			`$(RUBY) extconf.rb --vendor`
build: integrate building ruby bindings into notmuch build process 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. 2015-06-01 09:08:59 +02:00			`$(MAKE) -C $(dir)/ruby`
			`endif`

			`CLEAN += $(patsubst %,$(dir)/ruby/%, \`
			`.RUBYARCHDIR.time \`
			`Makefile database.o directory.o filenames.o\`
			`init.o message.o messages.o mkmf.log notmuch.so query.o \`
			`status.o tags.o thread.o threads.o)`