mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-21 21:52:10 +02:00
autotools: Automate regenerating docs
Don't rely on hardcoded path to wikitext but instead use maven to download it and call ant properly. Moved to latest 3.0.22 wikitext. Regenerated the help with the latest wikitext too. To auto regenerat one has to call maven with -PregenHelp. Change-Id: Ie30779dfa4bd1c52dfa20411f810c96288daf509 Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
This commit is contained in:
Alexander Kurtakov
parent
964e738381
commit
35bf85ebde
12 changed files with 78 additions and 42 deletions
|
|
@ -28,7 +28,7 @@
|
|||
<td style="width: 60%" align="center"></td>
|
||||
<td style="width: 20%" align="right" valign="top">Make Targets</td>
|
||||
</tr>
|
||||
</table><hr/>
|
||||
</table><hr class="navigation-separator"/>
|
||||
<h1 id="Building">Building</h1>
|
||||
<p>As mentioned, an Autotools project is an extended CDT Makefile project. Building the project is done the same as for any Makefile project. You can kick off a build manually by clicking on the Project -> Build Project menu item or if you choose, you can set up builds to occur automatically when resources are changed by checking off the Project -> Build Automatically menu item. The former build option is disabled when automatic builds are selected. By default, a
|
||||
<b>make all</b> is performed following the Autotools configure step.
|
||||
|
|
@ -83,7 +83,7 @@
|
|||
<p>
|
||||
<img border="0" src="images/AutotoolsProperties.png"/>
|
||||
</p>
|
||||
<p>Note: changes to configurations are not performed unless the Ok or Apply buttons are pressed from a Property page with the Manage Configurations button on it. That is, pressing Ok from the Manage Configurations dialog does not make the changes permanent. You could add new configurations, delete others, and then hit the Cancel button from the corresponding property page and the changes would be reverted.</p><hr/>
|
||||
<p>Note: changes to configurations are not performed unless the Ok or Apply buttons are pressed from a Property page with the Manage Configurations button on it. That is, pressing Ok from the Manage Configurations dialog does not make the changes permanent. You could add new configurations, delete others, and then hit the Cancel button from the corresponding property page and the changes would be reverted.</p><hr class="navigation-separator"/>
|
||||
<table class="navigation" style="width: 100%;" border="0" summary="navigation">
|
||||
<tr>
|
||||
<td style="width: 20%" align="left">
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@
|
|||
<td style="width: 60%" align="center"></td>
|
||||
<td style="width: 20%" align="right" valign="top">Invoking Autotools</td>
|
||||
</tr>
|
||||
</table><hr/>
|
||||
</table><hr class="navigation-separator"/>
|
||||
<h1 id="Configuration">Configuration</h1>
|
||||
<p>Prior to running a build, the Autotools plug-in runs the configure script. Parameters to be passed to configure may be
|
||||
entered via the Project -> Properties -> Autotools -> Configure Settings UI shown below:</p>
|
||||
|
|
@ -96,7 +96,7 @@
|
|||
<p>The Autotools console is an instance of a CDT Build console so the console preferences set in Window -> Preferences -> C/C++ -> Build Console apply as well.</p>
|
||||
<p>
|
||||
<img border="0" src="images/AutotoolsBuildConsole.png"/>
|
||||
</p><hr/>
|
||||
</p><hr class="navigation-separator"/>
|
||||
<table class="navigation" style="width: 100%;" border="0" summary="navigation">
|
||||
<tr>
|
||||
<td style="width: 20%" align="left">
|
||||
|
|
|
|||
|
|
@ -28,20 +28,24 @@
|
|||
<td style="width: 60%" align="center"></td>
|
||||
<td style="width: 20%" align="right" valign="top">Configuration</td>
|
||||
</tr>
|
||||
</table><hr/>
|
||||
</table><hr class="navigation-separator"/>
|
||||
<h1 id="Creating_an_Autotools_Project">Creating an Autotools Project</h1>
|
||||
<p>There a number of ways to create an Autotools project. The first method is through the CDT C and C++ Project wizards which can be activated from the File -> New -> C Project and File -> New -> C++ Project menu items, respectively, which are available while in the C/C++ Perspective. These two wizards can also be located by clicking on the File -> New -> Project... menu item and then opening the C/C++ folder found there.</p>
|
||||
<p>There a number of ways to create an Autotools project. </p>
|
||||
<h2 id="Creating_New_Project_From_Scratch">Creating New Project From Scratch</h2>
|
||||
<p>The first method is through the CDT C and C++ Project wizards which can be activated from the File -> New -> C Project and File -> New -> C++ Project menu items, respectively, which are available while in the C/C++ Perspective. These two wizards can also be located by clicking on the File -> New -> Project... menu item and then opening the C/C++ folder found there.</p>
|
||||
<p>Looking at the C Wizard, we see that there is a GNU Autotools category.</p>
|
||||
<p>
|
||||
<img border="0" src="images/AutotoolsNewCProjectWizard.png"/>
|
||||
</p>
|
||||
<p>Opening the category, there are three choices: Empty Project, Autotools Shared Library Project, or Hello World Ansi C Autotools Project. The Empty Project template means that no files will be supplied to the new project while the Hello World project will supply a sample hello world program that uses Autotools for configuring the build. The Autotools Shared Library project is an example of how to use Autotools to create a shared library. The C++ Project Wizard also has the same GNU Autotools category and the three project templates: an Empty Project, Autotools Shared Library, and a Hello World C++ Autotools sample program. If you are creating a project from scratch, it is recommended that you use either the Hello World sample project or the Autotools Shared Library sample project and make modifications. Otherwise, you will need to create a configure script for the Autotools plug-in to invoke at build time or provide a Makefile so the configuration step does not fail.</p>
|
||||
<h2 id="Creating_New_Project_When_Importing">Creating New Project When Importing</h2>
|
||||
<p>The C and C++ Wizards can also be used when importing an existing Autotools project. For example, when importing a project from CVS using File -> Import... -> CVS -> you are given the choice to "Check out as a project configured by the new project wizard".</p>
|
||||
<p>
|
||||
<img border="0" src="images/AutotoolsCheckOutAs.png"/>
|
||||
</p>
|
||||
<p>From the New Project menu, open the C/C++ category and choose either a C Project or C++ Project, depending on the type of project being imported. If the code is both C and C++, choose C++ Project.</p>
|
||||
<p>Let's say you have a C application using Autotools and select C Project. This will bring up the C Project Wizard as displayed earlier. In this case, choose the Empty Project from the GNU Autotools category as you already have all the configuration files in place.</p>
|
||||
<h2 id="Converting_Exist_Project_After_Importing">Converting Exist Project After Importing</h2>
|
||||
<p>Another method to create an Autotools project is to convert an existing project. For example, if we import a project from SVN or CVS and do not configure using the new project wizard, the project will simply be downloaded into the workspace. At this point, it cannot be built or access various tools from the CDT.</p>
|
||||
<p>To convert it, select the project in the Project Explorer and open the File -> New -> Convert to C/C++ Project menu item as found in the C/C++ Perspective. If in another perspective, this same wizard can be found by selecting File -> New -> Other... -> C/C++ -> Convert to a C/C++ Project. This brings up the C/C++ Conversion wizard.</p>
|
||||
<p>
|
||||
|
|
@ -49,6 +53,7 @@
|
|||
</p>
|
||||
<p>Note how there is a set of projects that are candidates for conversion. This list contains any projects that are not already C or C++ projects. A C or C++ project includes regular CDT Managed Make and Makefile projects. Also note that the project you selected is automatically selected when the wizard opens.</p>
|
||||
<p>There is a choice of C or C++ project and a set of project types to choose from. For Autotools, select the GNU Autotools category and this will convert to an Autotools project. Once converted, this project will not show up as a candidate project in the conversion wizard.</p>
|
||||
<h2 id="Converting_Exist_Project_.28Any.29">Converting Exist Project (Any)</h2>
|
||||
<p>The final way to create an Autotools project is to use the Autotools Conversion wizard. This wizard allows one to convert from any form of project to an Autotools project. Obviously, converting a project that isn't actually C or C++ and using Autotools will result in undefined behaviour. You need to first select the project you wish to convert. After selecting, go to File -> New -> Other... -> C/C++, open the category, select "Convert to a C/C++ Autotools Project" and hit the Next button. </p>
|
||||
<p>
|
||||
<img border="0" src="images/AutotoolsConvertWizard.png"/>
|
||||
|
|
@ -58,7 +63,7 @@
|
|||
<img border="0" src="images/AutotoolsConvertProject.png"/>
|
||||
</p>
|
||||
<p>Again, there are candidates for conversion. This list contains all projects that are not currently C or C++ Autotool projects. You are given the choice of C or C++ as with the standard C/C++ conversion wizard. Hitting the Finish button is all that is needed, but if you hit the Next button and continue on you can select referenced projects, if desired. </p>
|
||||
<p>Once converted to an Autotools project, there is no UI method to convert back to a regular C/C++ project. If this is desired, you need to manually remove the .project, .cproject, and .autotools files from the project directory. This will effectively remove the natures and CDT settings for the project, allowing you to convert it again however you want.</p><hr/>
|
||||
<p>Once converted to an Autotools project, there is no UI method to convert back to a regular C/C++ project. If this is desired, you need to manually remove the .project, .cproject, and .autotools files from the project directory. This will effectively remove the natures and CDT settings for the project, allowing you to convert it again however you want.</p><hr class="navigation-separator"/>
|
||||
<table class="navigation" style="width: 100%;" border="0" summary="navigation">
|
||||
<tr>
|
||||
<td style="width: 20%" align="left">
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@
|
|||
<td style="width: 60%" align="center"></td>
|
||||
<td style="width: 20%" align="right" valign="top">Special Editors</td>
|
||||
</tr>
|
||||
</table><hr/>
|
||||
</table><hr class="navigation-separator"/>
|
||||
<h1 id="Invoking_Autotools">Invoking Autotools</h1>
|
||||
<p>To invoke the Autotools, a special sub-menu has been added to the project Context menu. Select any file in the project and then click on Invoke Autotools. There you will find a set of menu items to invoke the various Autotools for your project. The output of the tool invocation is presented in a special Autotools Console. Like the Configure and C-Build Consoles, the Autotools console is per-project and is not saved across Eclipse sessions. The console, if present, can be accessed via the "Display Selected Console" button in the Console View.</p>
|
||||
<p>
|
||||
|
|
@ -38,7 +38,7 @@
|
|||
<ol>
|
||||
<li>Invoke Autoconf
|
||||
<ul>
|
||||
<li>The autoconf tool is run in the current directory for the current file or folder selected for the project. There are no parameters. Autoconf can also be run by right-clicking a configure.in or configure.ac file and selecting Invoke Autoconf.
|
||||
<li>The autoconf tool is run in the current directory for the current file or folder selected for the project. There are no parameters. Autoconf can also be run by right-clicking a configure.in or configure.ac file and selected Invoke Autoconf.
|
||||
<br/>
|
||||
</li>
|
||||
</ul>
|
||||
|
|
@ -100,7 +100,7 @@
|
|||
</p>
|
||||
<p>
|
||||
<img border="0" src="images/AutotoolsToolSettings.png"/>
|
||||
</p><hr/>
|
||||
</p><hr class="navigation-separator"/>
|
||||
<table class="navigation" style="width: 100%;" border="0" summary="navigation">
|
||||
<tr>
|
||||
<td style="width: 20%" align="left">
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@
|
|||
<td style="width: 60%" align="center"></td>
|
||||
<td style="width: 20%" align="right" valign="top">Updating This Document</td>
|
||||
</tr>
|
||||
</table><hr/>
|
||||
</table><hr class="navigation-separator"/>
|
||||
<h1 id="Make_Targets">Make Targets</h1>
|
||||
<p>A Makefile has a set of targets that can be built. Typically, every Makefile has an
|
||||
<b>all</b> target which builds all targets, but there may be optional targets as well. A CDT Makefile project enables one to invoke the various make targets via the Make Targets dialog. Since an Autotools project is a form of Makefile project, it too supports the Make Targets dialog.
|
||||
|
|
@ -73,7 +73,7 @@
|
|||
<p>
|
||||
<img border="0" src="images/AutotoolsModifyMakeTarget.png"/>
|
||||
</p>
|
||||
<p>The check-box that says "Run all project builders" should be left un-checked. By default, we only want the CDT Makefile builder to run and not the Autotools configure builder or any other builder.</p><hr/>
|
||||
<p>The check-box that says "Run all project builders" should be left un-checked. By default, we only want the CDT Makefile builder to run and not the Autotools configure builder or any other builder.</p><hr class="navigation-separator"/>
|
||||
<table class="navigation" style="width: 100%;" border="0" summary="navigation">
|
||||
<tr>
|
||||
<td style="width: 20%" align="left">
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@
|
|||
<td style="width: 60%" align="center"></td>
|
||||
<td style="width: 20%" align="right" valign="top">Building</td>
|
||||
</tr>
|
||||
</table><hr/>
|
||||
</table><hr class="navigation-separator"/>
|
||||
<h1 id="Special_Editors">Special Editors</h1>
|
||||
<p>The Autotools plug-in provides two special editors for editing Autotool input files. The first is the Autoconf Editor. This editor is invoked when opening configure.in, configure.ac files as well as the resultant configure scripts that autoconf creates. Support includes full colourization, outline view, rudimentary error parsing, and hover help/completion.</p>
|
||||
<p>
|
||||
|
|
@ -49,7 +49,7 @@
|
|||
<img border="0" src="images/AutotoolsAutomakeEditor.png"/>
|
||||
</p>
|
||||
<p>In the example shown, one can see the $ variable references are displayed when hovered over. This is particularly useful for $< and $@ in make targets to understand what is being referenced. In some instances, you will see reference to variables surrounded by the @ symbol (e.g. @srcdir@). This represents a variable that is to be substituted by the configure script.</p>
|
||||
<p>Rudimentary error parsing looks for syntax errors. As with the Autoconf editor, colourization can be controlled by preferences. Go to Window -> Preferences -> C/C++ -> Autotools -> Automake Editor and click on the Syntax tab.</p><hr/>
|
||||
<p>Rudimentary error parsing looks for syntax errors. As with the Autoconf editor, colourization can be controlled by preferences. Go to Window -> Preferences -> C/C++ -> Autotools -> Automake Editor and click on the Syntax tab.</p><hr class="navigation-separator"/>
|
||||
<table class="navigation" style="width: 100%;" border="0" summary="navigation">
|
||||
<tr>
|
||||
<td style="width: 20%" align="left">
|
||||
|
|
|
|||
|
|
@ -28,10 +28,10 @@
|
|||
<td style="width: 60%" align="center"></td>
|
||||
<td style="width: 20%" align="right" valign="top">Creating an Autotools Project</td>
|
||||
</tr>
|
||||
</table><hr/>
|
||||
</table><hr class="navigation-separator"/>
|
||||
<h1 id="Supported_Environments">Supported Environments</h1>
|
||||
<p>While the Autotools should work on any Unix-based system, it has only been extensively tested on Linux as the plugins originally came from the Linux Tools project. OS-specific bugs or problems that are not reproducible on Linux may require a user work-around. For example, users of Cygwin or MinGW may require setting modifications to get the plug-in working for their project. The Autotools plug-in is not supported under a regular Windows environment (i.e. without Cygwin or MinGW).</p>
|
||||
<p>To use the Autotools plug-in, it is required that you have the base CDT (C/C++ Development Tools) installed in Eclipse, the GNU Autotools installed on your system, and a "sh" (shell) command must be available. The "sh" command is required to invoke the configure script.</p><hr/>
|
||||
<p>To use the Autotools plug-in, it is required that you have the base CDT (C/C++ Development Tools) installed in Eclipse, the GNU Autotools installed on your system, and a "sh" (shell) command must be available. The "sh" command is required to invoke the configure script.</p><hr class="navigation-separator"/>
|
||||
<table class="navigation" style="width: 100%;" border="0" summary="navigation">
|
||||
<tr>
|
||||
<td style="width: 20%" align="left">
|
||||
|
|
|
|||
|
|
@ -24,12 +24,12 @@
|
|||
<td style="width: 60%" align="center"></td>
|
||||
<td style="width: 20%" align="right" valign="top"></td>
|
||||
</tr>
|
||||
</table><hr/>
|
||||
</table><hr class="navigation-separator"/>
|
||||
<h1 id="Updating_This_Document">Updating This Document</h1>
|
||||
<p>This document is maintained in a collaborative wiki. If you wish to update or modify this document please visit
|
||||
|
||||
<a href="http://wiki.eclipse.org/CDT/Autotools/User_Guide">http://wiki.eclipse.org/CDT/Autotools/User_Guide</a>
|
||||
</p><hr/>
|
||||
</p><hr class="navigation-separator"/>
|
||||
<table class="navigation" style="width: 100%;" border="0" summary="navigation">
|
||||
<tr>
|
||||
<td style="width: 20%" align="left">
|
||||
|
|
|
|||
|
|
@ -24,8 +24,7 @@
|
|||
<td style="width: 60%" align="center"></td>
|
||||
<td style="width: 20%" align="right" valign="top">Supported Environments</td>
|
||||
</tr>
|
||||
</table><hr/>
|
||||
<p></p>
|
||||
</table><hr class="navigation-separator"/>
|
||||
<h1 id="Introduction">Introduction</h1>
|
||||
<p>The Autotools plug-in for Eclipse is an optional feature of the CDT (C/C++ Development Tools) that adds support for maintaining and
|
||||
building C/C++ projects that use GNU Autotools. The Autotools plug-ins were migrated from the Linux Tools project into the CDT as part of the Eclipse Juno release.</p>
|
||||
|
|
@ -41,7 +40,7 @@
|
|||
<a href="http://www.gnu.org/software/autoconf/">http://www.gnu.org/software/autoconf/</a> and
|
||||
|
||||
<a href="http://www.gnu.org/software/automake/">http://www.gnu.org/software/automake/</a>
|
||||
</p><hr/>
|
||||
</p><hr class="navigation-separator"/>
|
||||
<table class="navigation" style="width: 100%;" border="0" summary="navigation">
|
||||
<tr>
|
||||
<td style="width: 20%" align="left"></td>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!--
|
||||
Copyright (c) 2012 Red Hat, Inc.
|
||||
Copyright (c) 2012, 2018 Red Hat, Inc.
|
||||
All rights reserved. This program and the accompanying materials
|
||||
are made available under the terms of the Eclipse Public License v1.0
|
||||
which accompanies this distribution, and is available at
|
||||
|
|
@ -18,15 +18,6 @@
|
|||
<property name="autotools.wiki.url.base" value="${autotools.help.doc.url.base}/CDT/Autotools"/>
|
||||
<property name="imageFolder" value="images"/>
|
||||
|
||||
<path id="wikitext.tasks.classpath">
|
||||
<!-- Replace dir with the dir you have wikitext installed into.-->
|
||||
<fileset dir="/usr/share/eclipse/dropins/mylyn-docs-wikitext/eclipse/plugins">
|
||||
<include name="org.eclipse.mylyn.wikitext.*core*.jar" />
|
||||
</fileset>
|
||||
</path>
|
||||
<taskdef classpathref="wikitext.tasks.classpath" resource="org/eclipse/mylyn/internal/wikitext/mediawiki/core/tasks/tasks.properties" />
|
||||
<taskdef classpathref="wikitext.tasks.classpath" resource="org/eclipse/mylyn/wikitext/core/util/anttask/tasks.properties" />
|
||||
|
||||
<target name="all" description="Generate Eclipse help content for the CDT Autotools user guide">
|
||||
<mediawiki-to-eclipse-help wikiBaseUrl="${autotools.help.doc.url.base}" title="Autotools Plug-in User Guide" formatoutput="true" dest="." templateExcludes="*eclipseproject*">
|
||||
|
||||
|
|
|
|||
|
|
@ -58,6 +58,41 @@
|
|||
</plugins>
|
||||
</build>
|
||||
</profile>
|
||||
<profile>
|
||||
<id>regenHelp</id>
|
||||
<build>
|
||||
<plugins>
|
||||
<plugin>
|
||||
<artifactId>maven-antrun-plugin</artifactId>
|
||||
<executions>
|
||||
<execution>
|
||||
<id>helpdocs</id>
|
||||
<phase>generate-resources</phase>
|
||||
<configuration>
|
||||
<target>
|
||||
<taskdef classpathref="maven.plugin.classpath"
|
||||
resource="org/eclipse/mylyn/wikitext/mediawiki/ant/tasks.properties" />
|
||||
<taskdef classpathref="maven.plugin.classpath"
|
||||
resource="org/eclipse/mylyn/wikitext/ant/tasks.properties" />
|
||||
<ant antfile="build-helper.xml" target="all" />
|
||||
</target>
|
||||
</configuration>
|
||||
<goals>
|
||||
<goal>run</goal>
|
||||
</goals>
|
||||
</execution>
|
||||
</executions>
|
||||
<dependencies>
|
||||
<dependency>
|
||||
<groupId>org.eclipse.mylyn.docs</groupId>
|
||||
<artifactId>org.eclipse.mylyn.wikitext.mediawiki.ant</artifactId>
|
||||
<version>3.0.22</version>
|
||||
</dependency>
|
||||
</dependencies>
|
||||
</plugin>
|
||||
</plugins>
|
||||
</build>
|
||||
</profile>
|
||||
<profile>
|
||||
<id>fake-doc</id>
|
||||
<activation>
|
||||
|
|
|
|||
|
|
@ -1,13 +1,19 @@
|
|||
<?xml version='1.0' encoding='utf-8' ?>
|
||||
<?NLS TYPE="org.eclipse.help.toc"?>
|
||||
<toc label="Autotools Plug-in User Guide">
|
||||
<topic href="CDT/Autotools/User_Guide/User-Guide.html" label="Introduction"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Supported-Environments.html" label="Supported Environments"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Creating-an-Autotools-Project.html" label="Creating an Autotools Project"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Configuration.html" label="Configuration"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Invoking-Autotools.html" label="Invoking Autotools"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Special-Editors.html" label="Special Editors"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Building.html" label="Building"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Make-Targets.html" label="Make Targets"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Updating-This-Document.html" label="Updating This Document"></topic>
|
||||
<toc topic="CDT/Autotools/User_Guide/User-Guide.html" label="Autotools Plug-in User Guide">
|
||||
<topic href="CDT/Autotools/User_Guide/User-Guide.html" label="Autotools Plug-in User Guide">
|
||||
<topic href="CDT/Autotools/User_Guide/User-Guide.html" label="Introduction"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Supported-Environments.html" label="Supported Environments"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Creating-an-Autotools-Project.html" label="Creating an Autotools Project">
|
||||
<topic href="CDT/Autotools/User_Guide/Creating-an-Autotools-Project.html#Creating_New_Project_From_Scratch" label="Creating New Project From Scratch"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Creating-an-Autotools-Project.html#Creating_New_Project_When_Importing" label="Creating New Project When Importing"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Creating-an-Autotools-Project.html#Converting_Exist_Project_After_Importing" label="Converting Exist Project After Importing"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Creating-an-Autotools-Project.html#Converting_Exist_Project_.28Any.29" label="Converting Exist Project (Any)"></topic>
|
||||
</topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Configuration.html" label="Configuration"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Invoking-Autotools.html" label="Invoking Autotools"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Special-Editors.html" label="Special Editors"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Building.html" label="Building"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Make-Targets.html" label="Make Targets"></topic>
|
||||
<topic href="CDT/Autotools/User_Guide/Updating-This-Document.html" label="Updating This Document"></topic>
|
||||
</topic>
|
||||
</toc>
|
||||
Loading…
Add table
Reference in a new issue