Re: cmake/build.mk?

[nia <nia%NetBSD.org@localhost>]

On Thu, Apr 29, 2021 at 10:06:37AM +0200, Thomas Klausner wrote:
> On Thu, Apr 29, 2021 at 08:05:24AM +0000, nia wrote:
> > On Wed, Apr 28, 2021 at 09:14:28PM +0200, Thomas Klausner wrote:
> > > On Wed, Apr 28, 2021 at 08:24:43PM +0200, Joerg Sonnenberger wrote:
> > > > On Wed, Apr 28, 2021 at 08:17:18PM +0200, Thomas Klausner wrote:
> > > > > I see that meson has a build.mk that defines the necessary override
> > > > > targets. cmake on the other hand is in mk with a USE_CMAKE setting
> > > > > (that mostly pulls in the dependency and some cmake default args).
> > > > 
> > > > I see cmake more as alternative to autoconf, so having it behave like
> > > > GNU_CONFIGURE sounds more sensible to me.
> > > 
> > > meson is also an alternative to autoconf...
> > >  Thomas
> > 
> > I assumed they were handled differently because pkgsrc assumes
> > a "configure" implementation uses make, while meson uses ninja.
> 
> I'd like to (optionally) use ninja with cmake as well...
>  Thomas

We could switch to using a build.mk-style solution for cmake so
it can be used with ninja too. I agree that the handling of
cmake in mk/configure is cluttered and confusing and the
separation meson has is cleaner.