If there were some kind of make-dep for lilypond it could even generate these dependencies automaticaly, like it happens for C (the compiler generates dependencies when passed the correct flags). This should not be too hard to brew up? Immanuel
On Tue, Sep 10, 2013 at 10:47 AM, Jacques Menu <[email protected]>wrote: > Hello Carl, > > An approach could be to create a makefile containing: > - the rules to compile LP files to PDF (fixed part); > - the dependencies among LP files reflecting the presence of > \include in them (variable part). > > Producing the makefile could be done by a script when your dropbox > changes, and you could then call "make" to compile whatever needs to be. > > JM > > Le 10 sept. 2013 à 10:04:54, ArnoldTheresius <[email protected]> a > écrit : > > > Carl Peterson-2 wrote > >> Question for those who are familiar with linux bash shell scripting... > >> > >> ... > >> > >> The question I have is whether it is possible to set up a similar script > >> to > >> "trace" a file's inclusion in other lilypond files and then compile > >> whenever an upstream file is loaded. My template/framework for hymn > >> settings uses discrete levels of file inclusions. > >> ... > >> Thanks, > >> Carl > >> > >> _______________________________________________ > >> lilypond-user mailing list > > > >> lilypond-user@ > > > >> https://lists.gnu.org/mailman/listinfo/lilypond-user > > > > I allready made a C program for Windows, which does a limited 'follow the > > \include files' to examine the file dates. Finally it starts lilypond > > (command line) if one of the source files found is newer than the > resulting > > PDF, otherwise it prompts for the question 'compile or not?'. > > This program is limited to > > - only files (source and result) in the current working directory are > > examined > > - the \include command must be the only one in the line (white space only > > allowed at the left), exactly one space to the string start '"' character > > - \include commands inside a comment block ( '%{' to '%}' ) will be > > examined, too. > > > > Unfortunately, this program is specialized for my use. I did try (but not > > complete) to implement some special features. There is very little > > documentation in the source code. > > Only if you have some experiance in C programming the source code can > help - > > but an experianced C programmer might be faster to build his own > 'ly-newer' > > command line program form scratch than by extending my program. > > > > Feel free to ask for the C source code, if you are still interested. > > > > ArnoldTheresius > > > > > > > > -- > > View this message in context: > http://lilypond.1069038.n5.nabble.com/Question-about-autocompile-bash-script-tp150528p150555.html > > Sent from the User mailing list archive at Nabble.com. > > > > _______________________________________________ > > lilypond-user mailing list > > [email protected] > > https://lists.gnu.org/mailman/listinfo/lilypond-user > > > _______________________________________________ > lilypond-user mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/lilypond-user >
_______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
