On 11 July 2016 at 13:48, David Kastrup wrote: > Mojca Miklavec writes: > >> PS/unrelated: Talking about macs, I don't like the fact that I have to >> create a script doing >> #!/bin/bash >> exec /Applications/LilyPond.app/Contents/Resources/bin/lilypond "$@" >> Why doesn't simple symlinking work? > > The difference will be the argv[0] that the executable is called with. > LilyPond apparently does not follow symlinks here since it has its own > symlink from out/bin/lilypond to lily/out/lilypond and calling the > symlink works while calling linked target does not: > > /.../ > > Arguably, following the symlink tentatively with readlink rather than > giving up altogether would make sense. readlink is very tiresome to > interpret, however, when it delivers a relative file name rather than an > absolute one, and using realpath will follow _all_ symlinks, and that > does not work in the out/bin/lilypond situation at least. > > And of course one needs the respective autoconf tests because clearly we > don't even have symlinks on all supported platforms (I'm fuzzy about > current Windows systems/filesystems). > > Basically: you have a point. It's just sort of an expensive point.
That's fine. If it's too expensive to implement, I would prefer seeing "functional improvements" to this one. Mojca _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
