Menu
▾
▴
#1686 Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available
Originally created by: *anonymous
Originally created by: ianhuli...@gmail.com
Originally owned by: ianhuli...@gmail.com
When running with Guile V2.*:
1. Add ability to run Lilypond to compile all the scheme files in /scm to produce /scm/out/*.go files. Add option -dcompile-scm-files so Lilypond can be run up to do this during build.
2. Add facilities to search and load compiled /scm/out/*.go first and only fall back to interpreting scm/*.scm file if this does not exist.
Originally posted by: ianhuli...@gmail.com
This will need changes in lily.scm -
add new compile routines for scheme and modify ly:load to pick up the .go file in preference to .scm;
also implement -d compile-scheme which will compile files when running with Guile V2.
Also changes in main.cc -
When running Guile V2, alter guile list %load-compiled-path as well as %load-path during start-up to find Lilypond files
also possibly %compile-fallback-path so Lily knows where Guile autocompile is putting its files.
Cheers Ian
Cc: pnorcks@gmail.com hanw...@gmail.com jan.nieuwenhuizen percival.music.ca@gmail.com
Status: Started
Originally posted by: percival.music.ca@gmail.com
(No comment was entered for this change.)
Labels: -Maintainability Type-Maintainability
Originally posted by: percival.music.ca@gmail.com
(No comment was entered for this change.)
Labels: -Type-Maintainability Type-Enhancement
Cc: -percival.music.ca@gmail.com
Originally posted by: ianhuli...@gmail.com
(No comment was entered for this change.)
Blocking: 1780
Originally posted by: ianhuli...@gmail.com
(No comment was entered for this change.)
Blocking: 1826
Originally posted by: ianhuli...@gmail.com
(No comment was entered for this change.)
Blockedon: 2025
Originally posted by: ianhuli...@gmail.com
(No comment was entered for this change.)
Blockedon: 2026
Originally posted by: ianhuli...@gmail.com
(No comment was entered for this change.)
Blockedon: -2025
Originally posted by: hanw...@gmail.com
(No comment was entered for this change.)
Cc: -hanw...@gmail.com
Originally posted by: pkx1...@gmail.com
(No comment was entered for this change.)
Labels: -Priority-High
Originally posted by: ianhuli...@gmail.com
(No comment was entered for this change.)
Blocking: -1826
Originally posted by: ianhuli...@gmail.com
Note to self:
Looks like we can't do the same trick to pre-pend to the %load-compiled-path list in Guile 2 as we did with %load-path (Faking a (set! %loadxxx (cons <newdirspec> %loadxxx)) in the main.cc code). Looks like we have to do the "approved" API method of setting the GUILE_LOAD_COMPILED_PATH env variable to <newdirspec> before the Guile Engine is initialized via scm_boot_guile.
Looks possibly like working round a bug in Guile 2.0.3 as the set! method works inconsistently on the Guile REPL. The only sure-fire way to do the pre-pend was to set the env variable.
Blockedon: -2026
Originally posted by: ianhuli...@gmail.com
Initial patch for code changes to lily/main.cc and lily/include/main.hh only available. The commit generating this patch is is currently on dev/guile-2. It has been tested on a Guile V1.8 system and passes regtests. Please review with an eye to merging this going through countdown etc. and eventually getting pushed to master branch via staging.
On Rietveld at http://codereview.appspot.com/6849088
Ian
Cc: dak@gnu.org
Originally posted by: ianhuli...@gmail.com
Patch with main.cc with comments etc. pushed to staging as
commit [r0898a8896b76e6e6dcbe0e037e9d434e96926d56]
Ian Hulin
Status: Fixed
Originally posted by: pkx1...@gmail.com
(No comment was entered for this change.)
Labels: -Type-Enhancement FIxed_2_17_10
Originally posted by: dak@gnu.org
Can't be Fixed_2_17_10, can it? That is already released without this patch AFAICS.
Originally posted by: PhilEHol...@googlemail.com
AFAICS, this was pushed to master on 18 January - after 2.17.10 and before 2.17.11. Updating label.
Labels: -FIxed_2_17_10 FIxed_2_17_11
Status: Verified