Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
dune-common
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Timo Koch
dune-common
Commits
a9638bee
Commit
a9638bee
authored
14 years ago
by
Christian Engwer
Browse files
Options
Downloads
Patches
Plain Diff
started to add some additional information on the dune specific
make ???check targets [[Imported from SVN: r6118]]
parent
135b8a68
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/buildsystem/buildsystem.tex
+35
-6
35 additions, 6 deletions
doc/buildsystem/buildsystem.tex
with
35 additions
and
6 deletions
doc/buildsystem/buildsystem.tex
+
35
−
6
View file @
a9638bee
...
...
@@ -918,14 +918,15 @@ make program, even those without a native {\em if} construct like GNU-make.
An automake
-
generated Makefile does not only know the usual
{
\em
all
}
,
{
\em
clean
}
and
{
\em
install
}
targets but also
\begin
{
itemize
}
\item
{
\bf
tags
}
travel recursively through the directories and create
\begin
{
description
}
\item
[
tags
]
travel recursively through the directories and create
TAGS
-
files which can be used in many editors to quickly find where
symbols
/
functions are defined
(
use emacs
-
format
)
\item
{
\bf
ctags
}
the same as "tags" but uses the vi
-
format for the tags
-
files
\item
{
\bf
dist
}
create a distribution tarball
\item
{
\bf
distcheck
}
create a tarball and do a test
-
build if it really works
\end
{
itemize
}
\item
[
ctags
]
the same as "tags" but uses the vi
-
format for the tags
-
files
\item
[
dist
]
create a distribution tarball
\item
[
check
]
run a set of regression tests
\item
[
distcheck
]
create a tarball and do a test
-
build if it really works
\end
{
description
}
\subsubsection
{
Building Documentation
}
\label
{
am
_
includes
}
...
...
@@ -1006,6 +1007,34 @@ the web page. This conversion can be done using inkscape
(
\url
{
http:
//
www.inkscape.org
/
}
)
.
\texttt
{
\$
(
top
\_
srcdir
)/
am
/
inkscape.am
}
offers the necessary rules.
\subsubsection
{
Automatic testing
}
Dune offers several special
\make
targets, which help you find problems
in you build system configuration, or in your code.
\begin
{
description
}
\item
[
check
]
You can define lists of regression tests in your
\makefileam
. These are run when you call
\texttt
{
make check
}
.
\item
[
distcheck
]
This target is already defined by automake. It
creates a tarball, unpacks it, tries to do an out
-
of
-
source build
and runs the regression tests against this build.
\item
[
sourcescheck
]
This target tries to make sure that you don't
forget to install any important headers or source files.
\item
[
headercheck
]
This target tries to make sure that your header
files can be parsed and are self contained.
\end
{
description
}
\minisec
{
The check target
}
TODO
\dots
{}
\minisec
{
The sourcescheck target
}
TODO
\dots
{}
\minisec
{
The headercheck target
}
TODO
\dots
{}
\subsection
{
configure.ac
}
\label
{
configure.ac
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment