Re: Issue 979 in lilypond: waf build system

[lilypond]

Comment #7 on issue 979 by Carl.D.Sorensen: waf build system
http://code.google.com/p/lilypond/issues/detail?id=979

waf has a node list, which is a set of file pointers in memory.  There  
cannot be a *node* with the same name
in the source directory and the build directory.  In fact, there is a  
method in the waf book that shows how one
can copy a file from the source directory to the build directory, and I've  
managed to make it work.

sorensen2:src Carl$ cat wscript
#! /usr/bin/env python
# encoding: utf-8

VERSION='0.0.1'
APPNAME='test'
srcdir = '.'
blddir = 'build'

def configure(conf):
        pass

def build(bld):
        bld.new_task_gen(source='c', target='d', rule='cp ${SRC} ${TGT}')
        bld.new_task_gen(
              rule = 'cp ${SRC}  
${SRC[0].parent.abspath(env)}/${SRC[0].name}',
              source = 'e')
sorensen2:src Carl$ waf
Waf: Entering directory `/Users/Carl/waftest/src/build'
[1/2] cp ${SRC} ${SRC[0].parent.abspath(env)}/${SRC[0].name}: e
[2/2] d: c -> build/default/d
Waf: Leaving directory `/Users/Carl/waftest/src/build'
'build' finished successfully (0.026s)
sorensen2:src Carl$ ls build/default
d       e


I think that it's working now with a workaround that calls the filesystem  
instead of using the node.

HTH,

Carl


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