That's not my understanding of the "add_custom_command()". For
"add_custom_command( TARGET )" it runs for the specified build events of
associated target. Which didn't work correctly for Visual Studio 2017 as I
mentioned.
For "add_custom_command( OUTPUT )" it'll run if OUTPUT is missing or
DEPEN
Ha that actually seems like a totally separate bug.
>From what I understand - if "add_custom_command()" is not associated with
any target and is just given a command it is supposed to run at build time
every time the build is initiated, but with the Visual Studio generator it
seems to just skip ov
I haven't tried it out but I'm not exactly surprised it wouldn't work with
Visual Studio 2017.
It seems to be similar to the issue mentioned here:
https://stackoverflow.com/q/54557801/1028434
The problem I noticed in the case of the StackOverflow question,
"add_custom_target(testcmake2 ALL)" does
By running "readelf -d " I have recently become aware
that the Debian Buster linker automatically turns all rpath requests
into runpath, and that runpath versus rpath difference apparently
creates some issues I am trying to debug for the PLplot OCaml binding
that did not appear for my previous (De
I have been following the examples in the "CMake Cookbook" by Radovan Bast
and Roberto Di Remigio and came across one example that doesn't appear to
work right on Windows.
The source code for these example can be found here:
https://github.com/dev-cafe/cmake-cookbook
Chapter-06/Recipe-07 is suppo