+1
-1
doc/builders/packages/urxvt.xml
+1
-1
doc/builders/packages/urxvt.xml
···
+1
-1
doc/languages-frameworks/beam.xml
+1
-1
doc/languages-frameworks/beam.xml
···-BEAM builders are not registered at the top level, simply because they are not relevant to the vast majority of Nix users.+BEAM builders are not registered at the top level, simply because they are not relevant to the vast majority of Nix users.To install any of those builders into your profile, refer to them by their attribute path <literal>beamPackages.rebar3</literal>:
+8
-9
doc/languages-frameworks/emscripten.section.md
+8
-9
doc/languages-frameworks/emscripten.section.md
···This mode is far more power full since this makes use of `nix` for dependency management of emscripten libraries and targets by using the `mkDerivation` which is implemented by `pkgs.emscriptenStdenv` and `pkgs.buildEmscriptenPackage`. The source for the packages is in `pkgs/top-level/emscripten-packages.nix` and the abstraction behind it in `pkgs/development/em-modules/generic/default.nix`.······-This `xmlmirror` example features a emscriptenPackage which is defined completely from this context and no `pkgs.zlib.override` is used.+This `xmlmirror` example features a emscriptenPackage which is defined completely from this context and no `pkgs.zlib.override` is used.······Using this toolchain makes it easy to leverage `nix` from NixOS, MacOSX or even Windows (WSL+ubuntu+nix). This toolchain is reproducible, behaves like the rest of the packages from nixpkgs and contains a set of well working examples to learn and adapt from.
+1
-1
doc/languages-frameworks/go.xml
+1
-1
doc/languages-frameworks/go.xml
···
+1
-1
doc/languages-frameworks/rust.section.md
+1
-1
doc/languages-frameworks/rust.section.md
···
+2
-2
doc/old/cross.txt
+2
-2
doc/old/cross.txt
······