Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
TTool
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Operate
Environments
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
mbe-tools
TTool
Commits
9dbc2f9d
Commit
9dbc2f9d
authored
7 years ago
by
Florian Lugou
Browse files
Options
Downloads
Patches
Plain Diff
added section about config file in dev_infrastructure documentation file
parent
7a4ec5b7
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/dev_infrastructure/ttool_development_infrastructure.tex
+41
-0
41 additions, 0 deletions
doc/dev_infrastructure/ttool_development_infrastructure.tex
with
41 additions
and
0 deletions
doc/dev_infrastructure/ttool_development_infrastructure.tex
+
41
−
0
View file @
9dbc2f9d
...
...
@@ -845,6 +845,47 @@ gradle :ttool:build
\end{verbatim}
if you only want to build TTool.
\subsection
{
Executing TTool
}
When TTool is executed, it fetches configuration settings from a
\texttt
{
config.xml
}
file and modifies it when closed. When you build TTool, a
default
\texttt
{
config.xml
}
file is copied from
\texttt
{
ttool/runtime/config.xml
}
to
\texttt
{
bin/config.xml
}
. As the
\texttt
{
bin
}
folder is not tracked by git, you can modify this configuration
file without committing your personal changes to the distant repository---which
you should not do. However, building TTool once again would replace your
personal
\texttt
{
bin/config.xml
}
with the generic
\texttt
{
ttool/runtime/config.xml
}
, losing the changes you made on your
configuration file.
A better way to use your personal configuration file through different TTool
builds is to keep your own copy of
\texttt
{
config.xml
}
outside of the
\texttt
{
bin
}
folder (which is removed when calling
\texttt
{
make ultraclean
}
).
You can either create your own configuration file anywhere on the repository and
be careful not to add it to be tracked by git, or put it in a location where it
would not appear when doing a
\texttt
{
git status
}
: either outside of the TTool
folder, or in a
\texttt
{
.ttool
}
subdirectory which is explicitly ignored by git:
\begin{verbatim}
$
mkdir .ttool
$
cp ttool/runtime/config.xml .ttool/
\end{verbatim}
You could thus either call ttool directly:
\begin{verbatim}
$
java
-
jar bin
/
ttool.jar
-
config .ttool
/
config.xml
\end
{
verbatim
}
or copy
\texttt
{
ttool.exe
}
to
\texttt
{
.ttool
}
subdirectory and modify it:
\begin
{
verbatim
}
$
cat .ttool/ttool.exe
#!/bin/sh
java -version
cd .ttool;
java -Xmx1024m -Djavax.net.ssl.trustStore=ServerKeyStore
\
-Djavax.net.ssl.trustStorePassword=123456 -jar ../bin/ttool.jar
\
-config config.xml -experimental -debug -avatar -uppaal -launcher
$
\end
{
verbatim
}
\subsection
{
Automated Tests
}
TODO
...
...
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