58 lines
1.5 KiB
ReStructuredText
58 lines
1.5 KiB
ReStructuredText
|
|
|
|
FAQ for users
|
|
=============
|
|
|
|
|
|
TL;DR How do I compile the code?
|
|
--------------------------------
|
|
|
|
::
|
|
|
|
$ python setup [-h]
|
|
$ cd build
|
|
$ make
|
|
|
|
|
|
How can I specify the compiler?
|
|
-------------------------------
|
|
|
|
By default the setup script will attempt GNU compilers.
|
|
You can specify compilers manually like this::
|
|
|
|
$ python setup --fc=ifort --cc=icc --cxx=icpc
|
|
|
|
|
|
How can I add compiler flags?
|
|
-----------------------------
|
|
|
|
You can do this with ``--extra-fc-flags``, ``--extra-cc-flags``, or
|
|
``--extra-cxx-flags`` (depending on the set of enabled languages)::
|
|
|
|
$ python setup --fc=gfortran --extra-fc-flags='-some-exotic-flag'
|
|
|
|
|
|
How can I redefine compiler flags?
|
|
----------------------------------
|
|
|
|
If you export compiler flags using the environment variables ``FCFLAGS``,
|
|
``CFLAGS``, or ``CXXFLAGS``, respectively, then the configuration will use
|
|
those flags and neither augment them, nor redefine them. Setting
|
|
these environment variables you have full control over the flags
|
|
without editing CMake files.
|
|
|
|
|
|
How can I select CMake options via the setup script?
|
|
----------------------------------------------------
|
|
|
|
Like this::
|
|
|
|
$ python setup --cmake-options='"-DTHIS_OPTION=ON -DTHAT_OPTION=OFF"'
|
|
|
|
We use two sets of quotes because the shell swallows one set of them
|
|
before passing the arguments to Python. Yeah that's not nice, but nothing
|
|
we can do about it on the Python side.
|
|
If you do not use two sets
|
|
of quotes then the setup command may end up
|
|
incorrectly saved in `build/setup_command`.
|