forked from mirrors/nixpkgs
115018ff15
Maybe there was an idea behind this separation, but looking at the contents I don't see any reason for these being separate.
33 lines
1.5 KiB
XML
33 lines
1.5 KiB
XML
<chapter xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xml:id="chap-language-support">
|
|
<title>Languages and frameworks</title>
|
|
<para>
|
|
The <link linkend="chap-stdenv">standard build environment</link> makes it easy to build typical Autotools-based packages with very little code. Any other kind of package can be accomodated by overriding the appropriate phases of <literal>stdenv</literal>. However, there are specialised functions in Nixpkgs to easily build packages for other programming languages, such as Perl or Haskell. These are described in this chapter.
|
|
</para>
|
|
<xi:include href="android.section.xml" />
|
|
<xi:include href="beam.xml" />
|
|
<xi:include href="bower.xml" />
|
|
<xi:include href="coq.xml" />
|
|
<xi:include href="crystal.section.xml" />
|
|
<xi:include href="emscripten.section.xml" />
|
|
<xi:include href="gnome.xml" />
|
|
<xi:include href="go.xml" />
|
|
<xi:include href="haskell.section.xml" />
|
|
<xi:include href="idris.section.xml" />
|
|
<xi:include href="ios.section.xml" />
|
|
<xi:include href="java.xml" />
|
|
<xi:include href="lua.xml" />
|
|
<xi:include href="node.section.xml" />
|
|
<xi:include href="ocaml.xml" />
|
|
<xi:include href="perl.xml" />
|
|
<xi:include href="python.section.xml" />
|
|
<xi:include href="qt.xml" />
|
|
<xi:include href="r.section.xml" />
|
|
<xi:include href="ruby.xml" />
|
|
<xi:include href="rust.section.xml" />
|
|
<xi:include href="texlive.xml" />
|
|
<xi:include href="titanium.section.xml" />
|
|
<xi:include href="vim.section.xml" />
|
|
</chapter>
|