blob: a260beb5104438b10704c6e3b54c2df77b59d5bb (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
|
{ pkgs, lib, emscripten, python }:
{ buildInputs ? [], nativeBuildInputs ? []
, enableParallelBuilding ? true
, meta ? {}, ... } @ args:
pkgs.stdenv.mkDerivation (
args //
{
pname = "emscripten-${lib.getName args}";
version = lib.getVersion args;
buildInputs = [ emscripten python ] ++ buildInputs;
nativeBuildInputs = [ emscripten python ] ++ nativeBuildInputs;
# fake conftest results with emscripten's python magic
EMCONFIGURE_JS=2;
configurePhase = args.configurePhase or ''
# FIXME: Some tests require writing at $HOME
HOME=$TMPDIR
runHook preConfigure
emconfigure ./configure --prefix=$out
runHook postConfigure
'';
buildPhase = args.buildPhase or ''
runHook preBuild
HOME=$TMPDIR
emmake make
runHook postBuild
'';
doCheck = true;
checkPhase = args.checkPhase or ''
runHook preCheck
echo "Please provide a test for your emscripten based library/tool, see libxml2 as an exmple on how to use emcc/node to verify your build"
echo ""
echo "In normal C 'unresolved symbols' would yield an error and a breake of execution. In contrast, in emscripten they are only a warning which is ok given that emscripten assumptions about shared libraries."
echo " -> https://github.com/kripken/emscripten/wiki/Linking"
echo "So just assume the dependencies were built using hydra, then YOU WILL NEVER see the warning and your code depending on a library will always fail!"
exit 1
runHook postCheck
'';
enableParallelBuilding = args.enableParallelBuilding or true;
meta = {
# Add default meta information
platforms = lib.platforms.all;
# Do not build this automatically
hydraPlatforms = [];
} // meta // {
# add an extra maintainer to every package
maintainers = (meta.maintainers or []) ++
[ lib.maintainers.qknight ];
};
})
|