Re: lost in trying to fine oll-core and or package.ily

[David Wright]

On Tue 15 Oct 2019 at 12:34:41 (-0400), Freeman Gilmore wrote:
> On Tue, Oct 15, 2019 at 11:37 AM David Wright <address@hidden> wrote:
> > On Tue 15 Oct 2019 at 10:28:36 (-0400), Freeman Gilmore wrote:
> > […]
> > > > I am not a programmer, but I am trying to understand the include
> > path.   Say
> > > > I clone here C:\openLilyLib\.   Then I want to use some files in
> > > > snippets; and I include the path C:\openLilyLib\snippets\.   Would that
> > > > include path give me access to all the files and subfiles in
> > snippets?   Would
> > > > setting the path to C:\openLilyLib\in the environmental variables do
> > > > anything for this?     This and any thing you may add to this topic
> > would
> > > > be useful to me.   So far Google has not cleared this up for me.
> >
> > It sounds as if you might be confusing the Environment Variable PATH
> > with "paths" (filenames) in general. LilyPond uses commandline switches
> > (-I) as described in the documentation. If you want some paths included
> > automatically, then the usual way to do this is to redefine your LP
> > command or run it from a script. For example, my script adds the
> > directories
> > --include="$HOME/LilyLib/" --include="$HOME/LilyLib/margins/"
> > --include="$HOME/LilyLib/parts-midis/"
> > to LP's search path, amongst other things. Those are "(absolute) paths
> > in general" or "directory names" and are in my home directory¹.
> >
> > But PATH is an operating system Environment Variable that determines
> > where the OS searches for programs to run, and typically looks
> > something like
> > /usr/local/bin:/usr/bin:/bin:/home/username/bin:/home/username/.local/bin
> > (the order might be different, and the above is in unix-style format).
> >
> > > I have seen this in other places; were do I do this?   Is this an
> > > Environment Variable setting, if so how?   How do i add C:\openLilyLib
> > *to*
> > > LilyPond's search path?   Else were most is explained but this but this
> > > step is left with no clue.
> >
> > ¹ HOME, like PATH, is an operating system Environment Variable, set
> >   to /home/username in this example. So "$HOME/LilyLib/" becomes
> >   /home/username/LilyLib/ when my script is executed.

> So your script is a header file?   And if it is a header file, then you do
> not have to use include ...'s?

No, it's not a header file, where what I understand as header files
are named …/filename.h and used for compiling programs. They typically
supply constants and the parameters for function calls (without
containing the code itself).

My script is a bash function, which is essentially just another way of
supplying a shell script to the system. It does a lot more than just
call LP (like finding the most up-to-date LP version, renaming MIDI
files so they collate sensibly, trashing the logfile when there are
no errors, etc). In this way, all I normally type for generating a
score is "lily filename".

> /home/ is like C:\?

Sometimes. /home/username is the directory in which username finds
themselves when they log in. Conventionally it's the top of the tree
of username's personal configuration files. On my system, all the
users' files are on a separate partition from the operating system.
I don't know the conventions for Windows users.

> Looks like you are specifying all the directories (sub.s are not included
> in the parent)?

That's correct. I have a stack of margin specifications, and
I routinely generate a set of MIDIs highlighting each part from a
simple include like \include "Midi-sattb.lily", which involves over
50 individual files to handle all my possible permutations. All this
stuff doesn't need to clutter my LilyLib directory.

Cheers,
David.