lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Delay import of `midi' module. (issue 297420043 by address@hidden)


From: David Kastrup
Subject: Re: Delay import of `midi' module. (issue 297420043 by address@hidden)
Date: Tue, 31 May 2016 14:37:22 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)

"Phil Holmes" <address@hidden> writes:

> Patchy-staging running now.
>>
>> https://codereview.appspot.com/297420043/

Well, hooray!  master has been pushed.  Now let's see whether this helps
James in any respect (if there is still a Ghostscript problem, it likely
won't, but otherwise it might).

And I need to stop LilyPond from conflating $(LD) for both C and C++.
In fact, it first proceeds to find a good version of LD for C, only to
have it stomped over with '$(CXX)' in STEPMAKE_CXX afterwards (commit
commit 078703a6ab29f75983a55ac2cc35fe5f315da574
Author: Jan Nieuwenhuizen <address@hidden>
Date:   Wed Oct 19 13:54:23 2005 +0000

    * stepmake/stepmake/*:
    * */GNUmakefile:
    * config.make.in:
    * GNUmakefile.in:
    * stepmake/aclocal.m4: Friendlier --srcdir build, allowing `make'
    from any directory in build-dir.  Cleanups.
    
    * make/srcdir.make.in: Remove.
    
    * lily/main.cc (setup_paths): Fix and document build-dir hack.
).

As I want to have 64bit compilation with C++ and 32bit with C on my
personal computer (don't ask), it's important to have the linker
distinguished properly.

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]