Have you thought about not doing anything in the root CMakeLists for your
testing directories but instead inside the active project you use
add_subdirectory ( it supports relative paths to handle directories not
physically nested inside it ).
On Wed, May 9, 2018 at 8:56 AM Job Noorman wrote:
> H
If you want an official CMake response, take it from Brad King himself:
https://gitlab.kitware.com/cmake/cmake/issues/16931
His second comment is interesting, I haven't tried the path of trying to
trick it into thinking it is an object file. That might be the way to go!
-Caleb
On Tue, May 15, 2
You are unfortunately out of luck here. CMake does not provide built in
functionality to create "fat" static libs (multiple static libs combined).
Visual Studio allows this quite easily but CMake does not. All static libs
are considered transitive dependencies and get carried through to
executable
Hi,
I am creating a static library which in turn depends on several other
libraries. So on Windows in Visual studio for my master library I have
updated Librarian section of project properties to add the other libraries
as additional dependencies. If I update Librarian section manually then I
am a
> I also wasn't able to find a way to get a list of targets a given target
depends on, so that I could run through it and query each dependent
target's custom property manually.
This isn't currently possible.
> The executable targets need to collect the shader files and headers of
only the libra
This is scheduled to be fixed in the next release by allowing OBJECT
libraries to be used in target_link_libraries.
On Tue, May 8, 2018 at 7:46 PM Miklos Espak wrote:
> Hi,
>
> I have an abstract class that I want to compile into many applications.
> Something like this:
>
> baseapp.h
> baseap
