File: appcompile.xml

package info (click to toggle)
listaller 0.5.9-4
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 8,096 kB
  • ctags: 1,611
  • sloc: xml: 11,195; ansic: 2,298; sh: 1,648; perl: 1,452; cpp: 1,289; java: 157; makefile: 134; cs: 48; python: 24
file content (32 lines) | stat: -rw-r--r-- 1,465 bytes parent folder | download
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
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "Listaller.ent">
%BOOK_ENTITIES;
]>

<section id="sect-Listaller-Packaging-Appcompile">
	<title>Appcompile</title>
		<para>
			Appcompile is a helper program to build applications from source-code.
			It will automatically detect the build-system, configure it (applying the necessary
			flags and custom ones), then build the applicatio and install it into a user-defined directory,
			so Listaller can use the binaries to generate an IPK package.
		</para>

	<section id="appcompile-whatis">
		<title>What is Appcompile?</title>
		<para>Appcompile is a helper program to build applications from source-code.
		It will automatically detect the build-system, configure it (applying the necessary flags and custom ones),
		then build the applicatio and install it into a user-defined directory, so Listaller can use the binaries to
		generate an IPK package.</para>
		<para>Using Appcompile is completely optional, it is not required to build IPK packages. However, in many cases it
		might simplify build-scripts a lot.</para>
	</section>

	<section id="howto">
		<title>How to use Appcompile?</title>
		<warning>
			<para>The documentation is not yet complete. You may want to help extending it.</para>
		</warning>
	</section>
</section>