1) I have a good build, have made a trivial modification, and it seems to work. (I found a class (Midi-duration) that’s unused. I commented it out, and everything builds fine. Since there’s no references to it, I presume the testsuites will be unaffected, though you never know... 2) I’m reading ‘contributor.pdf’. It says I will be assigned a mentor. That’s fine with me either way, but I’m curious if perhaps there’s some formal route I should go through at this point. 3) My plan is to work via the C++ files and improve the midi output. I see several .cc files with midi in their name and I think 4 header files with midi in the name.
So, at this point, I could use some advice about 1) where to focus in the contributor.pdf, and 2) some idea of the architecture, particularly with regard to midi processing. Of course, I could try to figure that out myself, but that doesn’t seem like the right approach. The first thing I need to do is understand what’s going on today before I muck with anything. -d > On Mar 26, 2016, at 8:54 AM, Carl Sorensen <c_soren...@byu.edu> wrote: > > On 3/26/16 9:49 AM, "lilypond-devel-bounces+c_sorensen=byu....@gnu.org on > behalf of Daniel Birns" <lilypond-devel-bounces+c_sorensen=byu....@gnu.org > on behalf of daniel.bi...@icloud.com> wrote: > >> What is LilyDev? > > http://www.lilypond.org/doc/v2.19/Documentation/contributor/lilydev > > > A Debian iso ready-to-go for doing LilyPond development. > > I used to maintain a usable lilypond development site on OS X. New > updates to OS X invariably broke the site and required hours or days of > fixing things. LilyDev in a VirtualBox VM always works, and works easily. > > I would really recommend using LilyDev in a VM. > > Carl > _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
