On 2024-04-11 1:14 pm, Wol wrote:
So it looks like it's searching the program directory for my include
files, and not the current directory where they actually are! Note that
running the older lilypond correctly compiles the file.
I am having trouble reproducing the behavior you are seeing. On a
Windows 10 machine (22H2, 19045.4170) that does not have Frescobaldi nor
any prior LilyPond installation, I took the following steps:
1) Download LilyPond for Windows (version 2.24.3, also 2.25.14 from the
development page)
2) Unzip to my Downloads folder (produced subfolders lilypond-2.24.3 and
lilypond-2.25.14)
3) Opened a terminal window within the Downloads folder...
4) Ran "lilypond-2.24.3/bin/lilypond --version" to verify the download
and extraction worked
5) Created two files on my Desktop:
%% test.ily %%
\version "2.24.0"
test = { b'4 4 2 }
%%%%
%% test.ly %%
\version "2.24.0"
\include "test.ily"
{ \test \test }
%%%%
6) Opened a terminal window within the Desktop folder...
7) Ran "..\..\Downloads\lilypond-2.24.3\bin\lilypond --version" to
verify pathing worked
8) Ran "..\..\Downloads\lilypond-2.24.3\bin\lilypond test.ly" to verify
compilation
At this point, test.pdf was created without any issues. (Well,
actually, it did fail due to a wrong version number, but that was
because I was running on autopilot and had mistyped the \version
statements in my test documents as 2.25.14, since I was also testing
against that version as well. Correcting the \version statements as
noted above resolved that.)
9) From an *elevated* command prompt...
10) Ran "assoc .ly=LilyPond"
11) Ran "ftype LilyPond=<full path to>\lilypond-2.24.3\bin\lilypond.exe
%1"
NOTE: The path above was to my user's Downloads folder from which I had
been running LilyPond during testing.
12) Back in a normal command prompt from the Desktop folder...
13) Ran "test.ly" to verify file association and compilation.
No issues.
14) Double-clicked "test.ly" from my Desktop.
No issues.
-- Aaron Hill
