That was it. I wound up finding a slightly different solution. I create a
static library of the resources, and then have the unit tests link in that lib.
Which gets the same dependency tree the custom target.
My question, that I'm still confused about is why this is necessary.
I have two proj
On 2019-01-19 00:09- Scott Bloom wrote:
I use qt + google test to run tests in my build environment.
The problem I have, is in some (most) of my unit test directories, there will
be multiple test executables created, all dependent on the same output file
from the add_resources step.
Typi
I use qt + google test to run tests in my build environment.
The problem I have, is in some (most) of my unit test directories, there will
be multiple test executables created, all dependent on the same output file
from the add_resources step.
Typically its something like
qt_add_resource( reso
Hey,
sending as requested; please find attached file...
my os: Win10 (updated)
build env. (msys2, updated)
project: spdlog (FOSS, last release)
The result was observed as follow:
- clone project
- mkdir build && cd build
- ccmake -G"MSYS Makefiles" ..
Thanks,
Lubomir.
# This is the CMakeCache f
