Skip to content
Snippets Groups Projects
Commit a43e6ec4 authored by graeser's avatar graeser
Browse files

Don't mention autotools anymore.

parent fb80c13d
Branches
No related tags found
No related merge requests found
Show whitespace changes
Inline Side-by-side
Showing
with 4 additions and 26 deletions
README
+ 4
− 26
View file @ a43e6ec4
...@@ -6,14 +6,6 @@ following programs installed on your system: ...@@ -6,14 +6,6 @@ following programs installed on your system:
cmake >= 2.8.6 cmake >= 2.8.6
or if you use the old autoconf build system:
automake >= 1.9
autoconf >= 2.62
libtool
Getting started Getting started
--------------- ---------------
...@@ -28,9 +20,8 @@ have to add the directory where the dunecontrol script resides (probably ...@@ -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. ./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 On your project and all uninstalled DUNE source modules found the script
will then calls the GNU autoconf/automake to create a ./configure-script will then call cmake. passing the required options for other dune-modules
and the Makefiles. Afterwards that configure script will be called and the automatically.
modules will be build using make all
Most probably you'll have to provide additional information to dunecontrol Most probably you'll have to provide additional information to dunecontrol
(e. g. compilers, configure options) and/or make options. (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 ...@@ -39,9 +30,6 @@ The most convenient way is to use options files in this case. The files
defining four variables: defining four variables:
CMAKE_FLAGS flags passed to cmake 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: An example options file might look like this:
...@@ -50,22 +38,12 @@ CMAKE_FLAGS=" \ ...@@ -50,22 +38,12 @@ CMAKE_FLAGS=" \
-DCMAKE_CXX_COMPILER=g++-4.9 \ -DCMAKE_CXX_COMPILER=g++-4.9 \
-DCMAKE_CXX_FLAGS='-Wall -pedantic' \ -DCMAKE_CXX_FLAGS='-Wall -pedantic' \
-DCMAKE_INSTALL_PREFIX=/install/path" #Force g++-4.9 and set compiler flags -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 If you save this information into example.opts you can pass the opts file to
dunecontrol via the --opts option, e. g. dunecontrol via the --opts option, e. g.
dunecontrol --opts=example.opts all 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 More info
--------- ---------
...@@ -76,5 +54,5 @@ See ...@@ -76,5 +54,5 @@ See
for further options. 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
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment