Skip to content

Add library path to LilyPond invocation#926

Merged
uliska merged 1 commit intomasterfrom
library-path
May 9, 2017
Merged

Add library path to LilyPond invocation#926
uliska merged 1 commit intomasterfrom
library-path

Conversation

@uliska
Copy link
Copy Markdown
Contributor

@uliska uliska commented Apr 11, 2017

This will fix a long-standing annoyance - but is only implemented with downloaded and self-compiled versions on Linux. I assume distro packages will work as well (or don't need it anyway), but I have no idea about Mac and Win. Maybe the problem doesn't apply to them, but I want to wait for feedback on that before merging this PR.

Not adding this can cause compilation failures when the bundled versions of libraries (like Ghostscript) don't match the system-provided ones.

Not adding this can cause compilation failures when the bundled
versions of libraries (like Ghostscript) don't match the system-provided
ones.

Note that this commit only is checked with downloaded and self-compiled
versions on Linux. I assume distro packages will work as well (or
don't need it anyway), but I have no idea about Mac and Win.
@uliska uliska requested a review from wbsoft April 11, 2017 09:01
@uliska
Copy link
Copy Markdown
Contributor Author

uliska commented Apr 11, 2017

There's one thing I'm not really sure about, and that's who abscommand and command relate, and if that's relevant to my patch

@uliska
Copy link
Copy Markdown
Contributor Author

uliska commented Apr 11, 2017

See also http://lists.gnu.org/archive/html/lilypond-user/2017-04/msg00236.html for the question of other OS/installation types

@uliska
Copy link
Copy Markdown
Contributor Author

uliska commented Apr 11, 2017

It seems the issue is no issue on Windows as probably all dependencies are bundled in the installer.

So that leaves OS X. I don't know how LilyPond is packaged/bundled there, but somehow I have the feeling it's bundled as well.

As I don't recall this error being raised by non-Linux users I think we can merge this patch and wait if any users raise the issue again.

@uliska uliska changed the title WIP: Add library path to LilyPond invocation Add library path to LilyPond invocation Apr 11, 2017
@uliska
Copy link
Copy Markdown
Contributor Author

uliska commented May 9, 2017

As I haven't got any further feedback I assume that

  • this issue is only relevant for Linux
  • the fix doesn't affect others either

So I'll merge this after fixing the indicated merge conflicts

@uliska uliska mentioned this pull request May 9, 2017
@uliska uliska merged commit aab7c3c into master May 9, 2017
@uliska uliska deleted the library-path branch May 9, 2017 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant