1
<page xmlns="http://projectmallard.org/1.0/"
3
id="autotools-project-backend">
5
<info xmlns:facet="http://projectmallard.org/facet/1.0/">
6
<facet:tag key="all-pages" value="whatever"/> <!--Include page in index-->
7
<link type="guide" xref="project-manager#backend"/>
9
Autotools project backend.
11
<credit type="author">
12
<name>Sébastien Granjoux</name>
13
<email>seb.sfo@free.fr</email>
15
<credit type="editor">
16
<name>Philip Chimento</name>
17
<email>philip.chimento@gmail.com</email>
21
<title>GNU Autotools project backend plugin</title>
24
This is the most common project format on Linux. It has been designed to
25
distribute source code packages on a wide range of Unix-like systems.
26
If you have ever installed a program using <cmd>configure</cmd>,
27
<cmd>make</cmd> and <cmd>make install</cmd>, you probably have already
32
It is typically a bit more difficult to use as a developer.
33
However, it is the default backend for <app>Anjuta</app>, which has features
34
that make it easier to use. All the project manager's features are enabled
36
You should be able to maintain a project using the Autotools backend without
37
writing a line in <file>configure.ac</file> or any <file>Makefile.am</file> files.
42
Autotools files give more information than a makefile, but the backend
43
does not support all the possible tricks. If you find a project that
44
cannot be read correctly, filing a <link
45
href="https://bugzilla.gnome.org/browse.cgi?product=anjuta">bug report</link>
47
In the meantime, as a workaround, you can use the directory project backend
48
instead. It is much more limited but should find all source files.
added
removed
manuals/anjuta-manual/C/autotools-project-backend.page
