Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
frama-c
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor 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
Charles Southerland
frama-c
Commits
01ec9c33
Commit
01ec9c33
authored
4 years ago
by
David Bühler
Browse files
Options
Downloads
Patches
Plain Diff
[Doc] User manual: mentions frama-c-script make-template earlier.
parent
babed390
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/userman/user-analysis-scripts.tex
+5
-4
5 additions, 4 deletions
doc/userman/user-analysis-scripts.tex
with
5 additions
and
4 deletions
doc/userman/user-analysis-scripts.tex
+
5
−
4
View file @
01ec9c33
...
...
@@ -76,8 +76,9 @@ and presents an illustrative diagram.
\subsection
{
Necessary Build Information
}
\label
{
sec:necessary-build-information
}
For an analysis with
\FramaC
, besides the source code, the following pieces
of information are necessary:
The command
\texttt
{
frama-c-script make-template
}
can be used to generate the
Makefile from a template. The user must fill in the following information,
required for running an
\Value
analysis:
\begin{description}
\item
[machdep]
: architectural information about system where the code will run:
...
...
@@ -93,8 +94,8 @@ of information are necessary:
a
\texttt
{
main
}
function, but plug-ins such as
\texttt
{
Eva
}
do
}
.)
\end{description}
A project without
such
information is incomplete
. In such cases,
an alternative
workflow is necessary. The next section presents some possibilities to
A project without
this
information is incomplete
;
an alternative
workflow is
then
necessary. The next section presents some possibilities to
retrieve such information.
\subsection
{
Possible Workflows in the Absence of Build Information
}
...
...
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