cafkafk/nixpkgs
cafkafk/nixpkgs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
nixpkgs/doc/languages-frameworks/index.xml

33 lines
1.5 KiB
XML
Raw Normal View History

nixpkgs manual: split languages into separate files There's no change in content except for amending the title of the section to mention "frameworks", as e.g. I don't consider Qt a language, and it's likely there will be more of similar cases in future. To be certain, I checked diff of the generated HTMLs.
2015-12-19 16:04:36 +01:00
<chapter xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xml:id="chap-language-support">
doc: organize chapters into parts, and reduce toc depth Reorganize the chapters into parts and reduce the TOC depth to make the TOC useful again. The top-level TOC is very brief, but that is fine because every part will have its own TOC. Section titles of languages/frameworks are also simplified to just the name of the language/framework.
2019-10-20 12:17:58 +02:00
<title>Languages and frameworks</title>
nixpkgs docs: format =)
2018-05-02 01:54:21 +02:00
<para>
doc: re-format
2019-09-18 22:12:54 +02:00
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.
nixpkgs docs: format =)
2018-05-02 01:54:21 +02:00
</para>
Add documentation section for Android
2018-11-18 14:44:23 +01:00
<xi:include href="android.section.xml" />
nixpkgs docs: format =)
2018-05-02 01:54:21 +02:00
<xi:include href="beam.xml" />
<xi:include href="bower.xml" />
<xi:include href="coq.xml" />
doc: merge package notes and package-specific notes Maybe there was an idea behind this separation, but looking at the contents I don't see any reason for these being separate.
2019-10-20 12:37:45 +02:00
<xi:include href="crystal.section.xml" />
<xi:include href="emscripten.section.xml" />
doc: add GNOME Closes: #16285
2018-03-06 18:14:37 +01:00
<xi:include href="gnome.xml" />
nixpkgs docs: format =)
2018-05-02 01:54:21 +02:00
<xi:include href="go.xml" />
<xi:include href="haskell.section.xml" />
<xi:include href="idris.section.xml" />
Add documentation for building iOS apps
2018-11-27 20:48:48 +01:00
<xi:include href="ios.section.xml" />
nixpkgs docs: format =)
2018-05-02 01:54:21 +02:00
<xi:include href="java.xml" />
<xi:include href="lua.xml" />
<xi:include href="node.section.xml" />
duneBuildPackage: document
2018-11-06 18:18:27 +01:00
<xi:include href="ocaml.xml" />
nixpkgs docs: format =)
2018-05-02 01:54:21 +02:00
<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" />
Add Titanium documentation section
2018-11-18 15:29:51 +01:00
<xi:include href="titanium.section.xml" />
nixpkgs docs: format =)
2018-05-02 01:54:21 +02:00
<xi:include href="vim.section.xml" />
nixpkgs manual: split languages into separate files There's no change in content except for amending the title of the section to mention "frameworks", as e.g. I don't consider Qt a language, and it's likely there will be more of similar cases in future. To be certain, I checked diff of the generated HTMLs.
2015-12-19 16:04:36 +01:00
</chapter>
Reference in a new issue Copy permalink