-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Infer information about the source tree from DUNE-CMake's config mode files #212
Comments
On Tue, Mar 19, 2013 at 04:56:31PM -0700, Roland Kaufmann wrote:
There are two package config files: one in ${PROJECT_BINARY_DIR} and one BTW: I did not have any problems using the DUNE's cmake modules as I admit that this is not the ideal case, but it should suffice for the |
Configured like this:
then run:
yields This is |
On Wed, Mar 20, 2013 at 07:11:53AM -0700, Roland Kaufmann wrote:
Actually I thought you were talking about CMake's package config files This is not special to the cmake branches. It is the same for the |
Is this still an issue and, if so, is there something that can be done about it? |
Yes, it is still an issue; no, we don't have to do anything because it works as it is now; yes, we can do something about it; but no, no-one wants to spend time on it. So, in conclusion, if you want to clear out the issue list before the release, this should probably just be closed as won't-fix. |
I'm not particularly hell-bent on clearing the list, but I do want to understand/know the status of most of the issues. A "won't-fix" could be the best solution, but I'll leave it open for now. Thanks for the update! |
I'll close this as won't fix since we quite clearly do not have to fix this and will not spend any effort on it. |
OPM cannot include DUNE-CMake in config mode because it also needs information about which definitions that should be added to config.h, so that the DUNE headers is preprocessed identical in all libraries.
The current version simply uses the same probe routines as for the Autotools version, with some additional hints to guess the source directory from the location of the binary files.
An improvement to this would be to include the config mode files ourselves to first gather more information about where the source tree is located. The PkgConfig files cannot be used, as they point to the intended install location of the library instead of the build tree.
The text was updated successfully, but these errors were encountered: