| |||||||||||||
KS2011: Afternoon topicsKS2011: Afternoon topicsPosted Oct 27, 2011 22:15 UTC (Thu) by nix (subscriber, #2304)In reply to: KS2011: Afternoon topics by Cyberax Parent article: KS2011: Afternoon topics
The installation isn't that bad. The "oh heck now I have to learn it and (possibly) learn enough Python to be getting on with *and* figure out how this one-package build system works just so I can set CFLAGS and libdir appropriately for my biarch system, since they used lib and I use lib64 or vice versa or something like that"... *that* is not nice at all. In fact it was sufficient reason for me to avoid scons (and everything that used it to build completely) until recently.
(Sure, the problem goes away if it's a Python package... but if it's a Python package, why the heck aren't they using distutils, which supports prefix and destdir and everything necessary already, with zero effort needed from the packager?)
(Log in to post comments)
KS2011: Afternoon topics Posted Oct 28, 2011 10:28 UTC (Fri) by Rudd-O (subscriber, #61155) [Link]
waf supports CFLAGS and all the GNU dirs.
You don't have to learn anything new to use waf. If you know how to use configure, you know how to use waf.
KS2011: Afternoon topics Posted Oct 28, 2011 16:50 UTC (Fri) by nix (subscriber, #2304) [Link]
No site-config files, which means I have to figure out which of the autoconfish variables I set are actually supported by waf (not many) and pass them on the command-line instead. Yes, it's a valid approach, but it *is* something new to handle and it does need special handling by packagers / autobuilders. You cannot treat it just like autoconf.
|
|||||||||||||