Sure, go ahead. Op di 23 jun. 2020 23:35 schreef Owen Lamb <owendl...@gmail.com>:
> There are just three files, so I'll go ahead and put them in flower/. > > One more minor thing--the files are .cpp and .h, which is a bit confusing > given they're not our standard extensions. Is it all right if I change the > extensions to .cc and .hh to match the rest of the files? > > Thanks, > Owen > > On Tue, Jun 23, 2020 at 12:39 PM Han-Wen Nienhuys <hanw...@gmail.com> > wrote: > >> On Tue, Jun 23, 2020 at 9:55 AM Jonas Hahnfeld via Discussions on >> LilyPond development <lilypond-devel@gnu.org> wrote: >> > >> > Am Montag, den 22.06.2020, 16:44 -0700 schrieb Owen Lamb: >> > > Thanks, everyone! It looks like jsoncpp should work well for LilyPond. >> > > >> > > I don't have experience with adding files from one project to another. >> > > Jonas, is this "Amalgamated" procedure what you were describing? >> > > >> https://github.com/open-source-parsers/jsoncpp/wiki/Amalgamated-(Possibly-outdated) >> > >> > Yes, that's what I did a few years back. I think there used to be >> > amalgamated versions of the releases, not sure if they vanished or I'm >> > just mistaken. In any case, I'd recommend using version 1.8.4; 1.9.x >> > will eventually lead to version 2.0, but the developers are not there >> > yet. >> > >> > >> > > If so, when instructions say to add the generated files to one's >> project, >> > > does that mean to just copy them into the lilypond-git directory >> somewhere? >> > >> > Pretty much that, yes. >> > >> > > Where would be a good place to put them? >> > >> > No clue. Historically, that sounds like a job for flower/, but I'm not >> > a fan of the current split between flower/ and lily/. Please get >> > opinions from other developers that have been involved longer than me. >> >> How many files are they? >> >> If there are many of them, we should have a separate subdirectory. If >> it's just a few, flower/ would be a good place. >> >> -- >> Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen >> >