| Age | Commit message (Collapse) | Author |
|---|
|
nix run nixpkgs#silver-searcher -- -G '\.nix$' -0l 'description.*"[Aa]n?' pkgs \
| xargs -0 nix run nixpkgs#gnused -- -i '' -Ee 's/(description.*")[Aa]n? (.)/\1\U\2/'
|
|
|
|
|
|
|
|
|
|
|
|
If not set, attempts to use emscripten fails when acorn is missing as a
dependency. These, from emscripten-node-modules, need to be available at
runtime.
|
|
|
|
https://github.com/emscripten-core/emscripten/releases/tag/3.1.43
https://github.com/emscripten-core/emscripten/releases/tag/3.1.44
https://github.com/emscripten-core/emscripten/releases/tag/3.1.45
|
|
|
|
|
|
|
|
|
|
|
|
For the GHC JavaScript backend, we'll use emscripten in place of
targetCC. To avoid having too much special logic for this, we'll make
the emscripten derivation look like the result of wrapCC as far as GHC
is concerned, i.e. we need targetPrefix and bintools.
For bintools, we'll just reexpose emscripten, as it has emar, the only
relevant bintools. That the other ones are missing doesn't matter in
practice, as the GHC build system won't attempt to use them.
targetPrefix can immediately be (ab)used to make sure GHC will correctly
call emcc etc. instead of plain cc.
|
|
|
|
|
|
|
|
|
|
* binaryen: 102 -> 105
* emscripten: 3.0.0 -> 3.1.10
* Backport emscripten-core/emscripten#16986 to fix emscriptenPackages.libxml2 build
* Fix patch url/hash
Co-authored-by: Will Cohen <willcohen@users.noreply.github.com>
Co-authored-by: Will Cohen <willcohen@users.noreply.github.com>
|
|
|
|
|
|
This has been synonymous for ~5y.
Note that many of these runCommand bindings are unused, but that's
ok for generated code.
|
|
Previously building applications/libraries with "--bind" would not be
covered by the cache.
|
|
|
|
binaryen: 96 -> 99
These updates must be in the same commit because emscripten depends on
a specific version of binaryen.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Instead, we have a new `gccForLibs`, which has the appropriate
definition for e.g. avoiding `x86_32` linking problems.
|
|
|
|
|
|
|
|
|
|
Lots of packages are missing versions in their name. This adds them
where appropriate. These were found with this command:
$ nix-env -qa -f. | grep -v '\-[0-9A-Za-z.-_+]*$' | grep -v '^hook$'
See issue #41007.
|
|
Most of these can easily be moved to subdirectories of other
directories. This helps reduce clutter in the main trees.
|
|
This changes the emscripten package so that it specifies the rev from
the binaryen repo to use, and sets it to always use the version that has
been tagged for use with that version of emscripten. This should force
future updates of emscripten to also update binaryen.
Binaryen can also be installed as a stand-alone package, so there's some
logic added to the binaryen package to allow building in both ways, and
distinguishing between them.
|
|
* trying to build emscriptenPackages not all fail
* reading the console.log it turns out python executable is not in place and that is why emconfigure didnt work
* backup commit
* much more targets are compiling now
* added common revisioning
* revision bump to 1.37.36 (not tested)
* fixed xmllint
* forcing unit testing, will implement the tests after i get home
* json_c test working
* added tests
* tiny fixes
* added documentation
|
|
ryantm/auto-update/emscripten-1.37.16-to-1.37.34"
This reverts commit 5c02b9ab330729d97dd34ecd0e474d93f847af74, reversing
changes made to 2f2ad74369d2f516786ca02e2dff37e7713629a8.
https://github.com/NixOS/nixpkgs/pull/35636#issuecomment-373171672
|
|
Semi-automatic update. These checks were performed:
- built on NixOS
- found 1.37.34 with grep in /nix/store/mdr47v3wdjmzic5c2nvdx5krdwl6bcxf-emscripten-1.37.34
|
|
|
|
|
|
|
|
|
|
|
