Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
7
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Open sidebar
dune-course
pdelab-exercise2-sol
Commits
341303f9
Commit
341303f9
authored
Sep 21, 2015
by
Dominic Kempf
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Enable all packages!
parent
5d390098
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
1 addition
and
82 deletions
+1
-82
CMakeLists.txt
CMakeLists.txt
+1
-0
README
README
+0
-73
dune/pdelab_exercise2_sol_dummy.hh
dune/pdelab_exercise2_sol_dummy.hh
+0
-2
src/CMakeLists.txt
src/CMakeLists.txt
+0
-7
No files found.
CMakeLists.txt
View file @
341303f9
...
...
@@ -16,6 +16,7 @@ include(DuneMacros)
# start a dune project with information from dune.module
dune_project
()
dune_enable_all_packages
()
# start of the block specific to this project
add_subdirectory
(
src
)
...
...
README
deleted
100644 → 0
View file @
5d390098
Preparing the Sources
=========================
Additional to the software mentioned in README you'll need the
following programs installed on your system:
automake >= 1.5
autoconf >= 2.50
libtool
Getting started
---------------
If these preliminaries are met, you should run
dunecontrol all
which will find all installed dune modules as well as all dune modules
(not installed) which sources reside in a subdirectory of the current
directory. Note that if dune is not installed properly you will either
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
Most probably you'll have to provide additional information to dunecontrol
(e. g. compilers, configure options) and/or make options.
The most convenient way is to use options files in this case. The files
defining three variables:
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:
#use this options to autogen, configure and make if no other options are given
AUTOGEN_FLAGS="--ac=2.50 --ac=1.8" #Forces automake 2,50 and autoconf 1.8
CONFIGURE_FLAGS="CXX=g++-3.4 --prefix=/install/path" #force g++-3.4 as compiler
MAKE_FLAGS=install #Per default run make install instead of simply make
If you save this information into example.opts you can path 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
---------
See
dunecontrol --help
for further options.
The full build-system is described in the dune-common/doc/buildsystem (SVN version) or under share/doc/dune-common/buildsystem if you installed DUNE!
$Id: duneproject 6304 2011-01-04 18:53:16Z christi $
dune/pdelab_exercise2_sol_dummy.hh
deleted
100644 → 0
View file @
5d390098
#error This file only exists because of a peculiarity of DUNE's buildsystem.
#error It should never be included.
src/CMakeLists.txt
View file @
341303f9
add_executable
(
example02 example02.cc
)
target_link_libraries
(
example02
${
DUNE_LIBS
}
)
add_executable
(
example02b example02b.cc
)
target_link_libraries
(
example02b
${
DUNE_LIBS
}
)
add_dune_superlu_flags
(
example02b
)
add_executable
(
example02c example02c.cc
)
target_link_libraries
(
example02c
${
DUNE_LIBS
}
)
add_dune_alugrid_flags
(
example02c
)
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment