Re: [gentoo-dev] rfc: moving OpenRC to a meson-based build

[William Hubbs]

On Wed, Feb 01, 2017 at 09:03:49AM -0600, William Hubbs wrote:
> On Wed, Feb 01, 2017 at 11:54:41AM +0100, Tobias Klausmann wrote:
> > Hi!
> >
> > On Mon, 30 Jan 2017, William Hubbs wrote:
> > > I have been looking at the meson build system [1] [2], and I like what I
> > > see.
> > >
> > > I have opened an issue on OpenRC's github wrt migrating OpenRC to the
> > > meson build system [3].
> > >
> > > As I said on the bug, the downside is the addition of py3 and ninja as
> > > build time dependencies, but I think the upside (a build system where
> > > we don't have to worry about parallel make issues or portability)
> > > outweighs that.
> > >
> > > What do folks think here?
> >
> > Meson isn't even keyworded anywhere but amd64 and x86 and I
> > couldn't find an indication that they care about off-mainstream
> > architectures at all. Yes, it's written in Python as such is more
> > portable than if it were written in C or somesuch, but for a
> > build system, the arch it runs on and targets are more important
> > than for most other programs.
>
>  You are right that meson isn't keyworded anywhere but amd64 and x86,
>  and I will ask them about this because If they didn't want to support
>  off-mainstream arches this would be a blocker. Not just for OpenRC, but
>  for all consumers that convert to it.
 
 I checked with meson upstream, and they pointed me to Debian. Debian
 already has packages that use Meson on all arches such as
 https://packages.debian.org/sid/pitivi.

It looks like it would just be a matter of keywording meson as other
projects need it.

Again, the makefiles can't go anywhere at this point. this is an
upstream experiment to see how well meson would work.


William