Hendrick! That's exactly what I'm trying to do. Do you have an example
of the declaration of the dll import target setup you could share? That
would be immensely helpful.
Thanks
Walter
On 7/19/2014 4:01 AM, Hendrik Sattler wrote:
Hi,
for DLLs, the .lib part has it's own property IMPORTED_I
Hi,
for DLLs, the .lib part has it's own property IMPORTED_IMPLIB.
This is already the case for older versions of CMake but at least the Qt4 find
module makes no use of it.
In our own project, we use global imported targets with dll and import lib set
(and other properties like includes) and u
Thanks Nils!
The examples in the git repo are particularly helpful. It seems that in
all of the examples, the library type is being set to UNKNOWN. Is there
a reason for this? It seems that STATIC would be more suitable for most
of those, though the wording in the docs for IMPORTED_LOCATION [
On 07/18/2014 05:00 AM, Walter Gray wrote:
Hi list!
I'm a big fan of the new INTERFACE targets & target usage requirements,
but none of the provided Find.cmake files seem to take
advantage of the new paradigm. Checking the wiki, the old
Find.cmake seem to be deprecated, with most of the informa
Hi list!
I'm a big fan of the new INTERFACE targets & target usage requirements,
but none of the provided Find.cmake files seem to take
advantage of the new paradigm. Checking the wiki, the old
Find.cmake seem to be deprecated, with most of the information
on authoring new packages assuming
