Since FetchContent is essentially forwarding this on to ExternalProject, I suspect the problem exists for using ExternalProject directly too. I’m currently buried deep in refactoring ExternalProject code at the moment. I’d prefer to wait until I’ve got that done before looking into this problem, but it’s good to be aware of it while I’m doing that.
@Gilfoyle Could you report this as a new issue in the issue tracker please?