Differences between revisions 3 and 4
Revision 3 as of 2012-01-03 22:04:22
Size: 836
Comment: Fix URL
Revision 4 as of 2012-07-10 17:33:59
Size: 879
Editor: ?JaviMerino
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
mv .waf-*/waflib waflib mv .waf-*/* .
Line 18: Line 18:
Also, you will need to remove generated .pyc files during clean phase: Also, you will need to remove generated .pyc files during clean phase in the expanded dirs (waflib, wafadmin,...):
Line 21: Line 21:
find waflib -name "*.pyc" -delete find waflib wafadmin -name "*.pyc" -delete

Introduction

FTP Team decided it is not allowed to ship waf "binary" as-is into source tarballs available in main component of the archive.

waf "binary" is basically a Python script with an embedded bzip2 tarball unpacked at runtime. A more detailed explanation about it is available here.

How to unpack waf

Here is a quick-and-dirty recipe to generate a unpacked waf instance in your source tarball:

./waf --help &> /dev/null
mv .waf-*/* .
sed -i '/^#==>$/,$d' waf
rmdir .waf-*

Also, you will need to remove generated .pyc files during clean phase in the expanded dirs (waflib, wafadmin,...):

find waflib wafadmin -name "*.pyc" -delete