Re: cmake.port.mk and DEBUG

On Sun, Jan 21, 2018 at 06:00:24PM +0100, Jeremie Courreges-Anglas wrote:
> On Sat, Jan 20 2018, Stuart Henderson <stu@spacehopper.org> wrote:
>
> [...]
>
> > How about making the cmake debug-build stuff dependent on a
> > flavour (like "CMAKE_DEBUG") rather than making DEBUG do
> > double-duty as a compiler flag option *and* a cmake knob?
> >
> > (We already removed some other cases where DEBUG turned on
> > port-specific debug options..)
>
> Looks like several people agree with this direction, so here's a diff
> that adds MODCMAKE_DEBUG.
>
> Comments/oks?
>
>
> Index: share/man/man5/port-modules.5
> ===================================================================
> RCS file: /d/cvs/src/share/man/man5/port-modules.5,v
> retrieving revision 1.225
> diff -u -p -r1.225 port-modules.5
> --- share/man/man5/port-modules.5 2 Dec 2017 09:31:52 -0000 1.225
> +++ share/man/man5/port-modules.5 21 Jan 2018 16:58:03 -0000
> @@ -569,6 +569,13 @@ If set to `Yes', CMake will print detail
> stages about exact command being run, etc.
> Should not be used in ports Makefiles.
> Default value is `Yes'.
> +.It MODCMAKE_DEBUG
> +If set to `Yes', CMake will produce a debug build instead of a release
> +build.
> +The exact effects on the build process depend on settings specified in
> +the CMake config files.
> +Also files in the resulting package might named differently.

missing verb ? And i think, since ppl wont understand what it means....