Hello,
I’m experiencing an odd problem where no matter how I set CMP0093, it seems to
use the ‘NEW’ behaviour, breaking some other code relying on the OLD behaviour.
This is Cmake 3.15.4 from Homebrew, other people do report on other platforms
do report the policy working for them. Here’s my
> On 1 Oct 2018, at 14:25, Craig Scott wrote:
>
> You need to set CMAKE_OSX_DEPLOYMENT_TARGET as a cache variable before
> calling the project() command. If you set it as a normal (i.e. non-cache)
> variable, the compiler detection logic triggered by the project() call
> creates a cache
Hi,
The docs here:
https://cmake.org/cmake/help/v3.12/variable/CMAKE_OSX_SYSROOT.html
state that CMAKE_OSX_SYSROOT is computed from CMAKE_OSX_DEPLOYMENT_TARGET if
not explicitly set. Can anyone comment on how this works, because in my setup
it seems to be failing. This showed up as
Hi,
I was wondering if the official advice on re-running ‘configure_file’ has
evolved? There’s some answers on StackOverflow about using custom targets /
commands to force it but they seem … ugly.
Essentially I want configure_file to re-run each build - I still want the ‘only
update the
