debian/notmuch
1
0
Fork 0
mirror of https://git.notmuchmail.org/git/notmuch synced 2024-11-21 18:38:08 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
notmuch/bindings/Makefile.local

32 lines
898 B
Text
Raw Normal View History

emacs: Use makefile-gmake-mode in Makefile*s 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).
2020-08-08 13:49:49 +02:00
# -*- makefile-gmake -*-
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
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
ruby: improve compilation with CFLAGS The ruby MakeMakefile generates a makefile that is suboptimal, which has CFLAGS like this: CFLAGS = $(CCDLFLAGS) -march=x86-64 -mtune=generic \ -O2 -pipe -fno-plt -fPIC $(ARCH_FLAG) This works as long as the user doesn't modify the Makefile. Certain flags (namely -fPIC) need to be present regardless of what CFLAGS are specified. The Makefile should have done this instead: CFLAGS = -march=x86-64 -mtune=generic -O2 override CFLAGS += $(CCDLFLAGS) -pipe -fno-plt -fPIC $(ARCH_FLAG) Unfortunately they didn't, so we need to workaround their lack of foresight. We can simply add the necessary flags in the parent Makefile so everyone is happy. Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
2021-05-17 07:47:46 +02:00
$(MAKE) -C $(dir)/ruby CFLAGS="$(CFLAGS) -pipe -fno-plt -fPIC"
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
endif
build: optionally build python-cffi bindings Put the build product (and tests) in a well known location so that we can find them e.g. from the tests.
2019-10-20 03:52:56 +02:00
python-cffi-bindings: lib/$(LINKER_NAME)
ifeq ($(HAVE_PYTHON3_CFFI),1)
cd $(dir)/python-cffi && \
${PYTHON} setup.py build --build-lib build/stage && \
mkdir -p build/stage/tests && cp tests/*.py build/stage/tests
endif
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
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)
bindings: clean extra file created by ruby extension build system Noticed by dkg; this file seems to be created by building the debian package, and perhaps by other distro package builds.
2018-05-13 18:17:18 +02:00
CLEAN += bindings/ruby/.vendorarchdir.time
build: optionally build python-cffi bindings Put the build product (and tests) in a well known location so that we can find them e.g. from the tests.
2019-10-20 03:52:56 +02:00
CLEAN += bindings/python-cffi/build
Reference in a new issue Copy permalink