On 31/12/13 8:06 AM, Stuart Henderson wrote:
It's a huge mess, but at least there's a decent amount of knowledge
about how to work with it, both amongst packagers, and amongst (some ;)
upstream developers. And it's already been modified as needed to
handle things for OpenBSD.
Exactly, core autoconf and more of the related macros and so forth are
well supported on OpenBSD.
waf is at least not in m4 :]
waf seems at something like the stage of autoconf 2.13 or so, where
many people using it are patching it and want you to use their own
version, making it impossible to centralise any os-specific changes
that are needed.
IMO it is worse, at least with autoconf at the macro level it tended to
be relatively easy to copy things around and fix issues. With most
projects using WAF 1.5 and upstream being at WAF 1.7 and with the
differences between them it can be a bigger issue having issues fixed
between upstream and then back porting to projects local copies
of WAF 1.5.
If people are looking for a non-autoconf build system, cmake seems
about the best choice.. it's not perfect, but CMakefiles are fairly
readable, and it's nicely cross-platform..
Yes, CMake isn't perfect but its a fairly good start and going in
the right direction. Quite a few projects are using CMake or are
switching.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
