Commit Graph

13 Commits

Author SHA1 Message Date
Matthew Bauer
a79a8f29bc waf: use wafConfigureFlags for waf flags
This avoids the potential conflict between autoconf flags and the waf
flags. There is some overlap between the two but waf errors when it
doesn’t recognize the flag.
2019-04-09 23:44:37 -04:00
Symphorien Gibol
3d60a00c63 wafHook: cross compilation support
for this to work, wafHook must be in nativeBuildInputs.
2019-03-28 20:06:25 +01:00
Symphorien Gibol
1001d0034c wafHook: ignore configurePlatforms
waf does support --build and --host, but the only effect of these
options is an error message telling to use --cross-compile instead.
So we ignore these flags.
2019-03-28 19:59:16 +01:00
Symphorien Gibol
f23a21514c wafHook: ignore --disable-static and such options
These options are forcefully added by pkgsStatic but are not understood
by waf.
2019-03-28 18:33:08 +01:00
Symphorien Gibol
f075de5c25 wafHook: let derivations use an existing waf in a non-standard location
this is necessary for talloc
2019-03-28 18:32:29 +01:00
Benjamin Hipple
72c059fad6 waf: 2.0.10 -> 2.0.13 2018-12-06 00:14:53 +00:00
Matthew Bauer
92ebfa1383 wafHook: init
The waf build system is python-based and hosted locally in each package in the executable file named "waf". Unlike CMake, it cannot generate makefiles so we end up having to override the configure, build, and install phases. I've tried to keep these as close to what's in setup.sh as possible. If there is no waf file in the root directory, then we just copy the one hosted in Nixpkgs. Otherwise the only thing you have to add to a package using Waf is "wafHook" into nativeBuildInputs. wafFlags controls the flags specifically passed to waf while configureFlags, buildFlags, and installFlags are still used as in the generic builder.
2018-11-13 19:13:13 -06:00
Benjamin Hipple
32b11f423d waf: 2.0.6 -> 2.0.10
This commit also swaps the build tool to use python3 internally (which waf fully
supports and prefers) and swaps the src to be downloaded from gitlab. The waf.io
site only keeps source tarballs of the latest version, so once a new waf comes
out we can no longer reproduce older versions.

We need the ensureNewerSources hook to avoid this error, in both `python2` and `python3`:

    ValueError: ZIP does not support timestamps before 1980
2018-08-09 14:51:28 -04:00
volth
52f53c69ce pkgs/*: remove unreferenced function arguments 2018-07-21 02:48:04 +00:00
Ryan Mulligan
88d2722d5f waf: 2.0.4 -> 2.0.6
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:

- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 2.0.6 with grep in /nix/store/5rgayqfl64bn9pyrfsc9kcm2c4vdqybi-waf-2.0.6
- found 2.0.6 in filename of file in /nix/store/5rgayqfl64bn9pyrfsc9kcm2c4vdqybi-waf-2.0.6
2018-03-23 14:53:24 -05:00
Ryan Mulligan
2702a81533 waf: 1.9.0 -> 2.0.4
Semi-automatic update. These checks were performed:

- built on NixOS
- found 2.0.4 with grep in /nix/store/dr6xvrw483jr5vgznwpjj0hxx3jq86ha-waf-2.0.4
- found 2.0.4 in filename of file in /nix/store/dr6xvrw483jr5vgznwpjj0hxx3jq86ha-waf-2.0.4

cc "@vrthra"
2018-02-28 20:32:55 +00:00
Rahul Gopinath
021dd6a5f6 waf: 1.8.19 -> 1.9.0 2016-06-26 21:59:23 -07:00
tg(x)
310a20eda8 waf 2016-02-10 20:34:05 +01:00