On Thu, Aug 6, 2020 at 5:45 AM Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: > > FYI, the easiest and most portable fix is to add: > -B. > (followed by a space or some other whitespace) before the . or .. (source > directory) argument. (That basically undoes the effects of this pointless > incompatible macro change.) > Not only is that terrible advice, it's actually *wrong*. If you're going to do bad things like that, at least make sure to test it. If you're going to override the build directory with CMake like that to bypass the behavior (which you *should not do*), you actually will need to set both the source directory (with -S) and the build directory (with -B) to override the default setting that the macro sets. But note that attempting to force an in-source build or the old behavior will eventually break, since CMake upstream intends to disallow this eventually (hence all the warnings it throws when you try to do that). And a number of projects are already manually attempting to break legacy behavior in their CMakeLists. -- 真実はいつも一つ!/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx