Unless I'm mistaken, it says that the *CONVENTION* is to call
include_directories(${_INCLUDE_DIRS}) manually, not that
it is done automatically. To get that kind of automatic include
directory adding you need to have an import or interface target with
INTERFACE_INCLUDE_DIRECTORIES defined by t
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 [
http://www.cmake.org/Wiki/CMake:How_To_Find_Libraries#How_package_finding_works
seems to indicate if _FOUND is found, the
_INCLUDE_DIRS is passed to the include_directories() command,
and _LIBRARIES is passed to target_link_libraries()
Why is the reduced-case code below calling g++ without includ
Hello,
I've just subscribed to the list with the intent of developing, contributing
and maintaining a module for FindPyQt. I'm a long time packager/maintainer of
Sip4/PyQt4/PyQt5/QScintilla2 and such in Debian and Ubuntu. I've also working
packaging PyKDE4 (which uses CMake).
There is an exi
Hi everybody
I'm currently working with the 2.8.12.2 CMake version, and have an issue with
the Visual Studio 10 Win64 Generator.
In The CMakeLists.txt file I use to generate an executable, I've added
SET (CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} /STACK:134217728,32768")
CMake generato
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
