Re: [Denemo-devel] MXE denemo build

[Jeremiah Benham]

The sed portion of this script did not work. I don't know enough about sed to fix it. 

I have included lilypond in the denemo directory. It has a different prefix as denemo because some of the libs are not the same version. LilyPond is in denemo/LilyPond and denemo is denemo/. We need to tell denemo where to find this lilypond executable. 

Jeremiah

On Sep 13, 2017 8:58 AM, "Richard Shann" <address@hidden> wrote:

On Wed, 2017-09-06 at 10:25 -0500, Jeremiah Benham wrote:
> It is all in my public_html directory. I think you can recusevely wget
> the usr/ directory.
ok, thanks - I think I'll leave trying this until I've upgraded to the
new Debian stable. I see that the new Debian stable has dropped LilyPond
(and Denemo I think) because of Guile 1.8 (even though Denemo will work
with Guile 2.x), but I don't think that'll prove a problem, just a bit
more to do. (I'm not getting much done at the moment, unfortunately).
>  I am going to try to automate the building of snapshots. Maybe I can
> automate just the denemo snapshot after every git update? Would that
> be more useful?
Well, by itself the trade-off for doing this is only positive if your
server is going to be doing something else useful overnight. What
*would* be (somewhat) useful would be to build from git with the
configure.ac modified in the way Johan Vromans is doing, so that the
version number has the git revision signature appended:

git clone git://git.savannah.gnu.org/denemo.git .
 mv configure.ac configure.ac~
 sed "s;^\\(AC_INIT(\\[.*\\], \\[\\)\\(.*\\)\\], \\(\\[.*\\])\\);\\1\\2-`git rev-parse --short HEAD`], \\3;" \ <
 configure.ac~ > configure.ac ./autogen.sh

That way we wouldn't need to bump the development version ...

Richard

>
>
> Jeremiah
>
>
>
>
>
> On Sep 1, 2017 11:29 AM, "Richard Shann" <address@hidden>
> wrote:
>         On Fri, 2017-08-25 at 08:24 -0500, Jeremiah Benham wrote:
>         > I am now able to build denemo in mxe. I ended up using the
>         same
>         > version of fluidsynth that gub uses. I use the same patches
>         as well. I
>         > now need to patch evince to look for its backend directory
>         using
>         > getenv(). I will probably need denemo to set this
>         environment variable
>         > when it is launched. Denemo will crash if the evince
>         backends are not
>         > found.
>
>         I've been offline for the past week hence the late reply. This
>         all
>         sounds very encouraging - is it ready for others to try out?
>
>         Richard
>
>
>