Re: Issue 979 in lilypond: waf build system

[lilypond]

Comment #8 on issue 979 by percival.music.ca: waf build system
http://code.google.com/p/lilypond/issues/detail?id=979

dev/gperciva, just pushed (after previously being deleted), contains the  
current
state of waf.  I have no clue what happened to dev/waf; that's a topic for  
-devel.


We need to link (not actually copy, but I've used cp since that's a simpler  
command)
Documentation/pictures/* into BLDDIR/Documentation/pictures/.  This is so  
that the
html docs in, say, BLDDIR/Documentation/web/*.html can point  
to ../pictures/foo.png
and have the image display.

That workaround looks iffy, but if we can abstract that somehow so that we  
can use
SRC and TGT (or WORKAROUND_TGT), then I guess that would be good enough.


Before anybody talks to the waf people again, please make sure you know why  
we want
to do this, convince yourself that we can't do it any other way, etc etc.   
This is
*not* an urgent issue, so if you're unfamiliar with our current waf build  
attempts
and how it might move forward, any discussion on the waf list will almost  
certainly
be a sub-optimal use of resources (both your time, and the waf people's  
time).


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings