Hello!
Are the header files of the shared library (DLL) listed as INTERFACE_SOURCES
for the library target? AFAIK, the only reason for header files to be
processed by AUTOMOC is to be part of the project. The only way that I know
of for adding library headers to the consuming project is by declari
Just a heads up, CMake 3.15 is introducing policy 91 which removes the
runtime library from the default set of flags, and instead has targets
establish what runtime they want.
For more information see:
https://cmake.org/cmake/help/v3.15/prop_tgt/MSVC_RUNTIME_LIBRARY.html
On Tue, Jun 18, 2019 at 1
On 18.06.19 12:53, David Aldrich wrote:
> I have a simple CMake project that builds an executable using Visual
> Studio 2017:
>
> Files
> # -- Add files to project. -- #
> ###
>
> file(GLOB SRC_FILES
> ${CPP_DIR_1
Hi all. For those of you working on Linux, I'm pleased to announce that
CMake is now available as a snap. This can be a great way to conveniently
keep up with the latest CMake releases, even on Linux distributions that
are no longer updating their own CMake packages. You can find a brief blog
post
I have a simple CMake project that builds an executable using Visual Studio
2017:
#==
cmake_minimum_required(VERSION 3.5 FATAL_ERROR)
### Variables.
# Change if you want modify path or other values. #
##
Dear all
It's a very long time I last posted here, so please be kind :-)
I currently am having a very hard time to get AUTOMOC to work properly
on WIN32 for the case where I have some Qt classes in a DLL that I
link to an executable. In this case, the header gets included by both,
the correspondi
