For older OpenSuSE versions (12.1 comes to mind), the packages mentioned
here are only available in the repository and not the base distro, so we
should start out by adding it instead of doing it later in the process.
If you just download the source, compile and install, you get the
release library. Users who want to develop the code, must do setup
in their environment.
Different set of packages may be necessary for various versions of the
RPM-based distros. Thus we need a way to know which one is indended to
be used (through the selection of the right url).
Also add a version number to the stem of the URL, so that later aliases
can be introduced to let one stay at previous versions.
Using headers and libraries from a DUNE built with different options
than OPM, can result in strange ABI errors such as a segmentation
fault in the static initialization section.
Load average of 0.9 is something that even a PhD student's crappy
laptop computer should be able to handle, without completely killing
it.
It really should be something like:
make -j -l $(echo \($(grep "^processor" /proc/cpuinfo)+1\)\*0.9 | bc)
but that is probably far too complex to put in a README. The average
developer should be able to pick a reasonable value themselves.
A large portion of the instructions was for building DUNE from source
without providing any real benefit for someone starting with OPM
development.
Instead provide a link to a repository where backports of the necessary
packages can be downloaded. This will hopefully enable beginners to get
up to speed faster.
On Debian Squeeze/Ubuntu Precise, the DUNE libraries does not come
pre-compiled, so the instructions should show how to download the
DUNE prerequisite library and how to compile it, using its special
system.
