On Thursday 16 February 2012, Alexander Neundorf wrote:
Hi,
when I use a Find-module to search for a package, I get a nice error
message if the package could not be found.
I collected the various error messages which can be produced in the
different
cases:
* package not found
* package
On Friday 17 February 2012, Rolf Eike Beer wrote:
On Thursday 16 February 2012, Alexander Neundorf wrote:
...
What should be improved:
1.), 2.), 4.) processing should stop if REQUIRED was used
I disagree. Say I want to build $random package. Throw the source
somewhere, run cmake. Now I
On Friday 17 February 2012, Alexander Neundorf wrote:
...
What should be improved:
...
2.) CMAKE_PREFIX_PATH should be mentioned
1.), 2.) if a version number was used, this should be printed in the error
message
1.) CMAKE_PREFIX_PATH should be mentioned at least.
These three points and a
Hi,
when I use a Find-module to search for a package, I get a nice error message
if the package could not be found.
If I use
find_package(Foo)
and rely on Config-mode, cmake produces an error message which doesn't help
the user:
~/src/extra-cmake-modules/example/b$ make rebuild_cache
Running
On 2/16/2012 8:19 AM, Alexander Neundorf wrote:
Comments, objections ?
The entire point of find_package's interface is that the caller
does not need to care how the package is found, and the actual
method used for the find can change under the hood.
Ideally every package would provide a
On Thursday 16 February 2012, Brad King wrote:
On 2/16/2012 8:19 AM, Alexander Neundorf wrote:
Comments, objections ?
The entire point of find_package's interface is that the caller
does not need to care how the package is found, and the actual
method used for the find can change under the
On 2/16/2012 10:30 AM, Alexander Neundorf wrote:
In any of the above modes the error message can be more explicit.
It is up to the author of the project to choose to do this. I do
not want it to be required.
Here we disagree. I think it should be required, to avoid the impression
finding
