Ok, it seems the the key was to call bld.rescan(node) after adding it. I'm off to a short conference tomorrow. I expected to have internet access, but when I mentioned it to one of the professors today, he just laughed at me. :( so if I'm not around for a few days, that's why.
I'm going to work on 1) the waf build 2) merging the two init-pl files. in the dev/gperciva branch. I don't know how much time I'll have, but it's traditional for me to do build system stuff at conferences. I have no plans on touching anything else, so if you're waiting for me to do anything, either do it yourself or keep on waiting. Cheers, - Graham On Thu, Nov 12, 2009 at 5:54 PM, Graham Percival <gra...@percival-music.ca> wrote: > On Thu, Nov 12, 2009 at 10:21:16AM +0100, John Mandereau wrote: >> Le jeudi 12 novembre 2009 à 00:21 +0100, John Mandereau a écrit : >> > Does the attached patch convince you to go on on Waf? >> >> Actually, please ignore my patch and checkout a SVN copy of Waf instead >> >> svn checkout http://waf.googlecode.com/svn/trunk/ && mv trunk waf >> >> then invoke waf-light from this checkout. > > I'm already working from waf. I did an svn update. It still > fails the first time I run it, while working perfectly the second > time. > > In case there's any misunderstanding, I'm talking about the > dev/gperciva branch. The minimal example that Thomas Nagy sent > works just fine. > > > 1) if you can't duplicate the problem after checking out > dev/gperciva, then I'll check a third time to see if there's any > old version of waf floating around on this machine. > > 2) if you can duplicate it in dev/gperciva, then please either > fix the problem in my wscripts, or follow up with the waf people > (if you can extract another small example). > > Cheers, > - Graham > _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
