Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
dune-functions-debug
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
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
graeser
dune-functions-debug
Commits
a43e6ec4
Commit
a43e6ec4
authored
9 years ago
by
graeser
Browse files
Options
Downloads
Patches
Plain Diff
Don't mention autotools anymore.
parent
fb80c13d
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README
+4
-26
4 additions, 26 deletions
README
with
4 additions
and
26 deletions
README
+
4
−
26
View file @
a43e6ec4
...
...
@@ -6,14 +6,6 @@ following programs installed on your system:
cmake >= 2.8.6
or if you use the old autoconf build system:
automake >= 1.9
autoconf >= 2.62
libtool
Getting started
---------------
...
...
@@ -28,9 +20,8 @@ have to add the directory where the dunecontrol script resides (probably
./dune-common/bin) to your path or specify the relative path of the script.
On your project and all uninstalled DUNE source modules found the script
will then calls the GNU autoconf/automake to create a ./configure-script
and the Makefiles. Afterwards that configure script will be called and the
modules will be build using make all
will then call cmake. passing the required options for other dune-modules
automatically.
Most probably you'll have to provide additional information to dunecontrol
(e. g. compilers, configure options) and/or make options.
...
...
@@ -39,9 +30,6 @@ The most convenient way is to use options files in this case. The files
defining four variables:
CMAKE_FLAGS flags passed to cmake
AUTOGEN_FLAGS flags passed to autogen
CONFIGURE_FLAGS flags passed to configure
MAKE_FLAGS flags passed to make
An example options file might look like this:
...
...
@@ -50,22 +38,12 @@ CMAKE_FLAGS=" \
-DCMAKE_CXX_COMPILER=g++-4.9 \
-DCMAKE_CXX_FLAGS='-Wall -pedantic' \
-DCMAKE_INSTALL_PREFIX=/install/path" #Force g++-4.9 and set compiler flags
AUTOGEN_FLAGS="--ac=2.50 --am=1.8" #Forces autoconf 2.50 and automake 1.8
CONFIGURE_FLAGS="CXX=g++-4.9 --prefix=/install/path" #Force g++-4.9 as compiler
MAKE_FLAGS=install #Per default run make install instead of simply make
If you save this information into example.opts you can pass the opts file to
dunecontrol via the --opts option, e. g.
dunecontrol --opts=example.opts all
To get a full list of available configure flags just run
dunecontrol configure --help
after running at least
dunecontrol autogen
More info
---------
...
...
@@ -76,5 +54,5 @@ See
for further options.
The full build-system is described in the dune-common/doc/buildsystem
(Git version) or under share/doc/dune-common/buildsystem if you installed DUNE!
The full build-system is described in the dune-common/doc/buildsystem
(Git version) or under share/doc/dune-common/buildsystem if you installed DUNE!
\ No newline at end of file
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