If you rely on it, add the deleted CMake files to your module.

The 'macroname' variable is still used by the code, but its definition
was accidentally removed together with the AutoTools-generating code.
Therefore, duneproject would fail with

/home/sander/dune/dune-common/bin/duneproject: Zeile 695: dune-foo/cmake/modules/: Ist ein Verzeichnis

This patch puts the missing definition back in.

These are the *.la files below dune and the primary module library
lib<module name without dashes>.la.

This reverts commit 21dbaefe.
Thus if libtool libs are found, then we abort again.
Please do not merge to the release.

Actually, having these files lying around does not hurt us.
In addition there are downstream modules that especially create
these for compatibility reasons with autotools. For these
reconfiguring a module using dunecontrol currently aborts with an error

Therefore this commit resorts to just issuing a warning and proceeding
with the compilation instead of aborting with an error.

Add missing files, remove ancient buildsystem stuff and stuff where it is
unclear where it comes from.

dune_enable_all_packages() now requires CMake 2.8.12, so make sure
duneproject generates a correct template.

Also output a warning to tell the user about this change in required
CMake version.

The shell script logic for switching dune_enable_all_packages() on or
off in duneproject was broken and always turned the feature on, ignoring
the user input.

Fixed by testing for the actual contents of the variable instead of its
length and by converting the contents to lowercase before.

Viz., the question on whether all packages should be enabled by default.

This fixes FS 1647.

A typo made it impossible to say 'no'.

Furthermore, I changed the text shown to the user to point to the
module documentation.

Claus-Justus Heine authored 9 years ago and Christoph Grüninger committed 9 years ago

Although GNU find may allow to omit the directory
argument, an ordinary (e.g. BSD) find does not.

Commit 	29405741 accidentally changed the file
permissions to non-executable.

Felix Gruber authored 10 years ago and Christoph Grüninger committed 10 years ago

The install path for header files can be configured in CMake with the
variable ${CMAKE_INSTALL_INCLUDEDIR}.

if the user has for some reason old la files from the autotools era,
these can lead to very subtle and hard to understand errors. We now
check for old la files and bail out in case some are found.

Previously, the command vcsetup, which is executed on command 'all',  was not
listed on the help screen.

This reverts commit 9f9bc5c0.

see FS#1576

Felix Gruber authored 10 years ago and Christoph Grüninger committed 10 years ago

Otherwise UNAME_HH was seen by the shell as the name of the variable,
but actually, the variable is called UNAME and _HH should be appended
after expansion of the variable.

Follow up to the previous patch: if the source file contains hyphens, then
the compiled executable should not have them replaced by underscores.

Each module constructed by duneproject contains a little Hello-world example
program.  The name of the program used to be the name of the module with .cc
appended AND all hyphens replaced by underscores.  Hence a module dune-foo
would containt the program dune_foo.cc.  This patch removes that displacement.
Rationale:
- I see no reason for the replacement in the first place
- File names with hyphens appear to be much more common in Dune world than
  file names with underscores.

Felix Gruber authored 10 years ago and Christoph Grüninger committed 10 years ago

add missing @

We fix the option handling when calling "cmake --build", by prepending '--' to the command
line parameters, in order to separate cmake and build parameters, iff the user didn't alrready do
it himself so. Note that this means we assume that the users generally want to pass
parameters to the build command and not to cmake itself.

This reverts commit eb045a4d.

As it severly breaks using the make build system. See
https://dune-project.org/flyspray/index.php?do=details&task_id=1572

mention cmake and CMAKE_FLAGS. Add an example for CMAKE_FLAGS in the
example opts file. Also update the compiler version in the example opts
file to a version that is actually supported by dune.

this makes new automake versions work like old automake versions. Some
of my projects used to compile objects in subdirs from parent directories.
New automake versions don't allow this. We don't want to atopt our
projects to changes in automake and make the transition to cmake... so
keep the old behaviour, by adding this option.

Previously this was only set if run_default_configure was executed
before. Ergo dunecontrol make did try to use cmake even if USE_CMAKE=no
was set. This fixes flyspray 1560.
https://dune-project.org/flyspray/index.php?do=details&task_id=1560

It sets LOCAL_USE_CMAKE for the current module depending on USE_CMAKE
and whether there actually is CMake support for this module.
This will make it more easy to use the same check in all run_*
directives.

This propbably the best spot to safe the user from himself!