#295 Should config.h be installed?
Metadata
| Property | Value |
|---|---|
| Reported by | Markus Blatt (markus@dr-blatt.de) |
| Reported at | May 16, 2007 07:24 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Nov 15, 2008 18:02 |
| Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Closed at | Nov 15, 2008 18:02 |
| Closed in version | 1.1 |
| Resolution | Implemented |
| Comment |
Description
Sven brought this up yesterday:
Apperently no config.h files get installed from the tarballs (probably the same is true for the installation from svn).
This means that it is not possible to compile an application from the installed dune without making a dune-project.
The question is now: Should we install the config.h files (and possibly rename them to common_config.h, etc.) making it possible for users to simply compile their applications without autoconf and others?
I think this should be possible even though there might be a lack of flexibility for the user, which he can regain by making a dune-project.