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 the script ./autogen.sh which calls the GNU autoconf/automake to create a ./configure-script and the Makefiles. Most probably you'll have to provide where to find the DUNE-files by ./autogen.sh --with-dune=PATH where PATH is a directory with a dune/-subdirectory inside (this convention is needed to keep the #include-syntax consistent even when the headers are installed into /usr/include/dune later). Passing options to ./configure ------------------------------ autogen.sh also calls the newly created configure-script to conveniently pass on options about the used compiler. Thus you'll have to provide autogen.sh any options you want configure to get, e.g. ./autogen.sh --with-dune=... --with-albert=... --without-x Choosing the compiler and the options ------------------------------------- The selection of the compiler works as follows: if --gnu or --intel is passed to autogen it reads the content of gcc.opts or icc.opts to get the default compiler flags. With the option --optim you can switch the compiler-specific optimization parameters on. If you want to change the compiler options to your favourites you can either - adapt the appropriate .opts-file and rerun autogen.sh. Please don't commit this changed file to CVS if you're not sure if the options work for everybody. - copy an existing .opts-file to a new name, change the options and use ./autogen.sh --opts=my.opts More info --------- See ./autogen.sh --help and (if it exists) ./configure --help for further options. The full build-system is described in the dune/doc/Buildsystem (not in duneapps/doc!) $Id$
"git@gitlab.mn.tu-dresden.de:osander/dune-gfe.git" did not exist on "f5c69b34eeb3ca7513182c04699ba79f1995a92a"
Oliver Sander
authored
To compute the derivative you need the function value (see my paper). Therefore, it is computed as the first thing in the evaluateDerivative method. However, frequently, the assembler also needs the function value, and also computes it. Hence the function value is computed twice. Since computing the function values takes quite a bit of time this patch removes that redundancy, at the price of a slightly more complicated API: if you happen to know the correct function value when calling evaluateDerivative, you can now hand over the value. Then evaluateDerivative uses that value instead of recomputing it. Short measurements have shown a speed increase between 25% and 45%. [[Imported from SVN: r8362]]