On Mon, 2013-02-18 at 19:10 +0000, Richard Shann wrote: > > Yes, I patched evince - then tried linked denemo with it and the pdf > backend. It fails because auto-tools has chosen to link with the C > library while the libpdfdocument.a requires C++. I am currently trying > to link to the C++ libraries. Then it looks like there is also cairo > stuff unresolved... >
I found a way to link using the g++ libraries, but it requires going back to the Makefile.am stage. You put nodist_EXTRA_denemo_SOURCES = dummy.cxx into Makefile.am in the src directory, and this causes it to use g++ for compiling the src files and hence links in the c++ libraries. I think I have this working with the git master branch. *BUT* whenever I generate a tarball from git master (using make dist) I get something which won't work inside mxe, this time I get make[3]: *** No rule to make target `../../denemo/libsmf/smf.c', needed by `libsmf_a-smf.o'. Stop before I was getting something similar with portaudio, or portmidi or some such. So, question: How are you generating the release candidate tarballs that appear on denemo.org/downloads? Without being able to create a tarball myself that will build with mxe I can't go back to the Makefile.am stage (as the tarball has that step already done). Richard _______________________________________________ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel
