Closed ebrightfield closed 4 years ago
I can confirm your assumption about user error and init.ily
.
One thing that comes to mind is: is <filename>
an absolute or relative path? And if the latter, is it a file in the current working directory or something like relative/path/to/file.ly
?
And, just to be complete: What operating system do you use?
I've tried to replicate your example, and although the error is not identical it seems close enough.
I get similar error messages when specifying the path to openLilyLib's root folder as a relative path from the current working dir, but not when it is given as an absolute path (this is on Linux).
I can very well imagine that this is the issue, and that an include path should be given as an absolute path.
@ebrightfield could you please check this. if it proves to be the issue I'll update the instructions accordingly.
Relative pathing was indeed the issue. When I changed the -I
flag's path to an absolute path, it worked.
I am running on Linux on x86, Manjaro 5.6.15-1.
I was not aware of that because Frescobaldi alwaya creates absolute paths.
I'll update the wiki page, thank youbfor reporting.
Fixed
To reproduce, follow instructions as stated in documentation, and execute a that looks like:
with the command
Yields the following output:
Something weird with the pathing, but I can't figure it out. I'm fairly sure it's not user error in the form of bad path in the
-I
flag, because I otherwise wouldn't be seeing errors frominit.ily
.