Re: does our cmake support really not use separate build dirs?

[Roland Illig <roland.illig%gmx.de@localhost>]

Am 17.08.2024 um 14:20 schrieb Greg Troxel:
> Taylor R Campbell <riastradh%NetBSD.org@localhost> writes:
>
>>> Date: Sat, 17 Aug 2024 08:00:00 -0400
>>> From: Greg Troxel <gdt%lexort.com@localhost>
>>>
>>> Adding USE_CMAKE=yes, I get a complaint that in-source builds are not
>>> supported.  Which is a bit much of upstream, but on the other hand
>>> nobody should be doing that either.
>>
>> Don't use USE_CMAKE=yes; use .include "../../devel/cmake/build.mk",
>> which works in a subdirectory called `cmake-pkgsrc-build'.
>
> I didn't get a warning from USE_CMAKE, and configure/cmake.mk doesn't
> warn about that either, so this is quite a mess.  Thanks for the hint.
>
> @rillig: If it turns out that doctrine really is "nobody should set
> USE_CMAKE", then perhaps warn on this....

Currently, the pkgsrc guide talks about devel/cmake/build.mk but does
not mention USE_CMAKE, and neither "bmake help topic=cmake" nor "bmake
help topic=use_cmake" point to any useful documentation. I'm not
familiar with CMake, so I'll wait for the "if it turns out" to become true.

For adding this migration to pkglint, I need a working and documented
migration path, preferrably in the pkgsrc guide.

Roland