bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 979 in lilypond: waf build system


From: lilypond
Subject: Re: Issue 979 in lilypond: waf build system
Date: Tue, 16 Mar 2010 03:27:23 +0000


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

Thomas Nagy (head waf developer) claims this is desired behavior -- i.e. you can't have a file in both blddir
and srcdir.


He suggests that you move the source file to another directory, e.g. a subdirectory of srcdir.

I tested a modification of the above and found that it worked:

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(source='subdir/e', target='e', rule='cp ${SRC} ${TGT}')


$ waf build
Waf: Entering directory `waftest/src/build'
[1/2] e: subdir/e -> build/default/e
[2/2] d: c -> build/default/d
Waf: Leaving directory `waftest/src/build'
'build' finished successfully (0.385s)

I don't know if this is helpful or not, but it's Thomas's recommended workaround.

The waf-user thread is here:
http://groups.google.com/group/waf-users/browse_frm/thread/8507c325d425b908#




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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]