On Wed, 7 Dec 2005, Graham Percival wrote:
I don't understand most of these patch,
I'll try to explain:
@echo export PATH=$(PATH)
+ @echo export LILYPOND_DATADIR=$(LILYPONDPREFIX)
@echo export LILYPONDPREFIX=$(LILYPONDPREFIX)
@echo export PYTHONPATH=$(PYTHONPATH)
This is needed so that lilypond does not try to use
/usr/local/share/something, but the files from where lilypond is compiled.
That makes it definitely unsuitable for general purpose distribution. This location can be overridden at runtime anyway, can't it?
diff --git a/my-lexer-gcc-3.1.sh b/my-lexer-gcc-3.1.sh
new file mode 100644
@@ -0,0 +1,10 @@
+cd "$(dirname "$0")/lily"
+rm out/lexer.cc 2>/dev/null
+mv out/lexer.cc out/lexer.cc.orig
+cat out/lexer.cc.orig | sed 's/^class istream;$/#include <iostream>\
+using namespace std;/' > out/lexer.cc
This is a very simple fix for my very special setup. Unless someone
verifies that it helps on other platforms, too, I'd rather see it as "it
helped me, maybe it helps you" hint.
This is definitely needed on MacOS, since flex generates a file that is not correct C++ on that particular point (I wonder why, and why this never causes problems on other platforms). I don't think that it hurts on any platform.
@@ -3,10 +3,14 @@ ARFLAGS = ru
ALL_LDFLAGS = $(LDFLAGS) $(CONFIG_LDFLAGS) $($(PACKAGE)_LDFLAGS)
PIC_FLAGS = -fpic -fPIC
-SHARED_FLAGS = -shared
SHARED_FLAGS = -mdll
+SHARED_FLAGS = -bundle -flat_namespace -framework Python
+SHARED_FLAGS = -shared
o-dep-out = $(outdir)/$(subst .o,.dep,$(notdir $@))#
I agree with Han-Wen that this should go into python-vars.make.
Actually, the -framework Python should go there, but -bundle -flat_namespace belongs into compile-vars IMHO.
@@ -111,3 +111,8 @@ endif
MINGW_BUILD = yes
+DARWIN_BUILD = yes
I think this is more or less uncontroversial. It defines the variable
DARWIN_BUILD on Darwin, so that the Makefiles can have special casing for
Darwin as they have special handling of MinGW.
Good idea. I should have proposed that a long time ago.