|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
Replicate port system for another use
Hello,
I have lots of music scores in the form of lilypond source files. When I need a score, I go in the directorie and compile it into a pdf. Those .ly are organised as such: artist/album/*.ly And I have some files responsible for the score layout that needs to be include in every .ly. Suddenly it hit me. It looks like the ports infracture of ours BSDs. So I am plannng of adaptating the ports system to my music scores in order to benefit from the advantages (compiling a whole album or artist in one command). Where should I start? Is there anything I should read (like the porters handbook)? Thanks. Last edited by Funkygoby; 21st June 2016 at 06:33 PM. Reason: Solved |
|
|||
Off hand, sounds like overkill. The ports system is designed to support building packages for many types of build systems, languages, and for different architectures.
Sounds like you just need a build tool in which you can define dependencies. Make, maven, scons, gradle, ant, and many more exist. Most are easier when used with their targeted language but can work with anything. Some are very generalized. This might be simple enough to get away with using a shell script. If you tried to use the build system, you'd be creating make files already, anyway. Tim. |
|
|||
Quote:
In general, make(1) is the only tool you need besides print/lilypond; that, and sufficient diskspace. The Makefile's might simply contain a rule looking at the timestamp of the resulting *.pdf files based on the *.ly & *.ily input files. Personally, any project I do in Lilypond is unique unto itself. I simply use devel/git to track changes for a single project. Yes, some tricks do get copied into new projects, but I have not seen the need for tying my projects so closely together, but your usage model may differ from mine. |
|
|||
Ok, it's overkill. Thank you for the insight, I didn't imagine the ports system did so much.
make(1) will do. I already have a Makefile for every .ly in there artist/album/title directories. With a little make(1) learning, I should obtain what I want. Here is some examples of possible improvements: -For starter, I would like to separate the build directory form the sources directories. Right now, I have unused/forgotten pdfs and midi files hanging with the .ly sources files. It's messy. -I have different files which are included at compile time depending on the music band I am targeting. -I want to centralize the redundant code -etc... list goes on. @ocicat: As a jazz sax player, most of my lilypond business is transcribing (sometimes composing) jazz tunes. It's basically melody+chords+few rhythm tags. Just like the realbooks... So I use a separate file that I include at compile time to mix that up and produce Ut, Eb and Bb versions + midi with chords down 1 octave. Then there are some sonata, counterpoint, song with lyrics, horn section, etc... which require different layout files. The only .ly that are self-sufficient (layout inside) are for occasional composing and experiments with custom formation. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Create MS/XP file system so it will be recognized on a XP system. | FBSD | Guides | 0 | 1st May 2010 06:49 AM |
SSH on port 443 | maxrussell | General software and network | 4 | 6th April 2009 05:16 AM |
port info | sniper007 | FreeBSD General | 6 | 14th November 2008 11:46 AM |
VNC port forwarding help | revzalot | OpenBSD Security | 3 | 10th September 2008 06:59 AM |
Which file system use to share data on Bsd system? | aleunix | Other BSD and UNIX/UNIX-like | 2 | 1st June 2008 04:14 PM |