Re: Issue 979 in lilypond: waf build system

[lilypond]

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

That's not good enough for our builds -- we want to make this easy for  
non-technical
doc-writers.  Adding a random subdir is going to break html docs.

If there's any desire to move forward on this, then we need somebody to  
convince
Thomas that this is a good feature.  Explain that we want to use waf to  
build
documentation; in particular, html docs.  Explain that we want to  
view/"test" our
docs by looking at files in the build dir.  Explain that our documentation  
writers
are non-technical idiots.  Explain that, in order for our doc people to be  
able to
figure out where the pictures are, we need the same directory structure in  
the output
directories as the source dirs.  Explain that this is a totally stupid  
arbitrary
decision on his part and that it's a dealbreaker for our use of waf.   
Suggest that he
could add a "--yes-we-are-idiots" flag to waf to enable the srcdir/builddir  
same-name
file option.  Discuss it with him and do whatever it takes to reach a  
resolution.

(ok, don't mention the "totally stupid arbitrary" part.  David: you're not  
eligible
for this diplomacy mission.  :)


--
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