aboutsummaryrefslogtreecommitdiffstats
path: root/community/binaryen/APKBUILD
Commit message (Collapse)AuthorAgeFilesLines
* [various]: unify names of licenses according to SPDXJakub Jirutka2017-12-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit updates $license variable in all APKBUILDs to comply with short names specified by SPDX version 3.0 [1] where possible. It was done using find-and-replace method on substrings inside $license variables. Only license names were updated, not "expressions" specifying relation between the licenses (e.g. "X and Y", "X or Y", "X and (Y or Z)") or exceptions (e.g. "X with exceptions"). Many licenses have a version or multiple variants, e.g. MPL-2.0, BSD-2-Clause, BSD-3-Clause. However, $license in many aports do not contain license version or variant. Since there's no way how to infer this information just from abuild, it were left without the variant suffix or version, i.e. non SPDX compliant. GNU licenses (AGPL, GFDL, GPL, LGPL) are especially complicated. They exist in two variants: -only (formerly e.g. GPL-2.0) and -or-later (formerly e.g. GPL-2.0+). We did not systematically noted distinguish between these variants, so GPL-2.0, GPL2, GPLv2 etc. may mean GPL-2.0-only or GPL-2.0-or-later. Thus GNU licenses without "+" (e.g. GPL2+) were left without the variant suffix, i.e. non SPDX compliant. Note: This commit just fixes format of the license names, no verification has been done if the specified license information is actually correct! [1]: https://spdx.org/licenses/
* community/binaryen: upgrade to 40Jakub Jirutka2017-12-281-3/+3
|
* community/binaryen: upgrade to 38Jakub Jirutka2017-10-311-5/+5
| | | | | | | | Moving to correct version number. Version 1.37.x is actually version of emscripten, not binaryen... https://github.com/WebAssembly/binaryen/issues/1156 https://github.com/WebAssembly/binaryen/pull/1173#discussion_r137853641
* community/binaryen: upgrade to 1.37.18Jakub Jirutka2017-08-151-2/+2
|
* community/binaryen: upgrade to 1.37.16Jakub Jirutka2017-07-211-2/+2
|
* community/binaryen: fix build on aarch64, armhf and ppc64leJakub Jirutka2017-06-211-2/+4
| | | | | This fix is just a temporary workaround! See https://github.com/WebAssembly/binaryen/issues/1059
* community/binaryen: upgrade to 1.37.14Jakub Jirutka2017-06-211-6/+4
|
* community/binaryen: disable on s390xTuan M. Hoang2017-05-131-1/+1
| | | | | | | | | | | | | | | | | | Probably bug in endianness detection. Fails in test: executing: bin/wasm-merge test/merge/dylib.wasm test/merge/dylib.wasm.toMerge \ -o a.wast -S --verbose --finalize-memory-base=1024 \ --finalize-table-base=8incorrect output, diff: --- expected +++ actual @@ -3,7 +3,7 @@ (import "env" "memory" (memory $0 1)) (table 2 2 anyfunc) (elem (i32.const 0) $__wasm_nullptr $__exit) - (data (i32.const 16) "\d2\04\00\00\00\00\00\00)\t\00\00") + (data (i32.const 16) "\00\00\04\d2\00\00\00\00\00\00\t)") Reported to upstream: https://github.com/WebAssembly/binaryen/issues/1012
* community/binaryen: upgrade to 1.37.12Jakub Jirutka2017-05-091-2/+2
|
* community/binaryen: upgrade to 1.37.10Jakub Jirutka2017-04-241-6/+3
|
* community/binaryen: move from testingJakub Jirutka2017-04-151-0/+56