[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: guilev2-work [was: LilyPond boolean syntax? \true and \false]
From: |
Thomas Morley |
Subject: |
Re: guilev2-work [was: LilyPond boolean syntax? \true and \false] |
Date: |
Mon, 11 Jan 2016 23:38:44 +0100 |
2016-01-11 23:14 GMT+01:00 David Kastrup <address@hidden>:
>> Btw, it wasn't entirely clear to me that guilev2.x changes essential
>> stuff that often.
>> Exactly which guile-version are we aiming for?
>
> The non-existing 2.0.12. Currently, the stable-2.0 branch. The main
> challenge currently seems to be compiling LilyPond with a Guile version
> that is not installed on your system.
>
> --
> David Kastrup
To be sure, the exercise is:
(1) checkout the marked branch
~/guile (master)$ git branch -a
* master
remotes/origin/HEAD -> origin/master
remotes/origin/branch_release-1-4
remotes/origin/branch_release-1-6
remotes/origin/branch_release-1-8
remotes/origin/cky-hygienic-macros
remotes/origin/historical/wip-1-8-mingw-build
remotes/origin/lloda-array-cleanup
remotes/origin/lloda-array-support
remotes/origin/lua
remotes/origin/master
remotes/origin/nan-boxing
remotes/origin/r7rs-wip
remotes/origin/stable-2.0
^^^^^^^^^^^^^^^^^^^^^^^^^^
remotes/origin/ttn-back-in-the-saddle
remotes/origin/wip-bpt-elisp
remotes/origin/wip-closure-conversion
remotes/origin/wip-compiler
remotes/origin/wip-cps-bis
remotes/origin/wip-dwarf
remotes/origin/wip-ethreads
remotes/origin/wip-finalizers
remotes/origin/wip-generalized-vectors
remotes/origin/wip-goops-refactor
remotes/origin/wip-nj-locks-nc
remotes/origin/wip-nj-thread-safety
remotes/origin/wip-raeburn-misc
remotes/origin/wip-retagging
remotes/origin/wip-rtl-cps
remotes/origin/wip-rtl-dwarf
remotes/origin/wip-rtl-halloween
remotes/origin/wip-rtl-may-2013
remotes/origin/wip-rtl-prompts
remotes/origin/wip-sassy
remotes/origin/wip-source-info
remotes/origin/wip-stime
remotes/origin/wip-streams
remotes/origin/wip-threaded-http-server
remotes/origin/wip-threads-and-fork
remotes/origin/wip-uri-reference
remotes/origin/wip-utf16-debugging
(2) Compile it
(3) Build LilyPond with this guile somehow
Correct?
Harm
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], (continued)
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], Ricardo Wurmus, 2016/01/09
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], Thomas Morley, 2016/01/10
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], David Kastrup, 2016/01/10
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], David Kastrup, 2016/01/10
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], Thomas Morley, 2016/01/11
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], David Kastrup, 2016/01/11
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false],
Thomas Morley <=
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], David Kastrup, 2016/01/11
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], David Kastrup, 2016/01/11
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], Thomas Morley, 2016/01/16
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], David Kastrup, 2016/01/16
- Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], Thomas Morley, 2016/01/19
Re: guilev2-work [was: LilyPond boolean syntax? \true and \false], David Kastrup, 2016/01/10