On 22/07/14 13:44, Stephen Kelly wrote:
>> Does this mean that if I set the _DIR environment variable to
>> the CMAKE_BINARY_DIR of my package, CMake will look into these folders
>> as well?
>
> No, I don't think so. You would have to set it to the exact dir afaik.
Actually I tested it, and CMake
The following issue has been SUBMITTED.
==
http://www.itk.org/Bug/view.php?id=15032
==
Reported By:Gerald Hofmann
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15031
==
Reported By:mscott
Assigned To:
=
Daniele E. Domenichelli wrote:
> Sorry, I'm still not convinced by this... The "QT_USE_FILE" variable
> will have the same issue with relative paths and will have to be passed
> as absolute path to configure_package_config_file(), or am I missing
> something?
Are you missing the assumption that i
On 22/07/14 10:53, Stephen Kelly wrote:
> Daniele E. Domenichelli wrote:
>
>> The first case is a folder that is appended to CMAKE_MODULE_PATH, and
>> that containing CMake files that can optionally be included by projects
>> using this package.
>
> I still find this an odd user interface.
>
> Y
Daniele E. Domenichelli wrote:
> The first case is a folder that is appended to CMAKE_MODULE_PATH, and
> that containing CMake files that can optionally be included by projects
> using this package.
I still find this an odd user interface.
You provide a variable FOO_MODULE_PATH or something and
On 21/07/14 21:04, Stephen Kelly wrote:
>>> Can you give a more-concrete example of what the problem is?
>>
>> The project is supposed to work both from build tree (using
>> export(TARGETS)) and from the install tree (using install(EXPORT)).
>
> Your example is too abstract. What is the meaning of
