Meson not in/not usable, but mentioned in release note of 1.12?

Martin Maurer meinemailingliste2 at
Fri May 5 06:39:15 UTC 2017


in release notes of 1.12, meson is mentioned as new/additional build system:

"Meson build files are now disted in tarballs, for jhbuild and so distro 
packagers can start using it. Note that the Meson-based build system is 
not 100% feature-equivalent with the autotools-based one yet."

I assume according to reply I got from Nirbheek (see below) that Meson 
is not usable in release 1.12?

Or were there some late changes for 1.12 to be able to use it?

Best regards,


-------- Weitergeleitete Nachricht --------
Betreff: 	Re: cerbero and Visual Studio/MSVC (under Windows 64 bit, for 
Windows 64 bit)
Datum: 	Mon, 24 Apr 2017 15:37:25 +0530
Von: 	Nirbheek Chauhan <nirbheek.chauhan at>
Antwort an: 	Discussion of the development of and with GStreamer 
<gstreamer-devel at>
An: 	Discussion of the development of and with GStreamer 
<gstreamer-devel at>

On Sun, Apr 23, 2017 at 11:52 PM, Martin Maurer
<meinemailingliste2 at> wrote:
> many thanks for your answer. How big is such an action?
> Just copying a few file or endless merging? Just to get a feeling...
> Do you think it still could be inside official release of 1.12
> to save you effort to merge it again and again?
> Or is it already too late for such an action?
> Is "time" the only blocking point, or still other things which must be
> clarified
> before it can go into an official release?

It's just a matter of getting the time to do it. It won't be in the
1.12 upstream release, but I hope to get it ready for the next one.

> I meanwhile went back to branch meson-1.10 and use this for initial
> (learning) steps.
> When 1.12 is ready for meson I can move to the new version.
> I have an additional question:
> Do I need to call
>> cerbero-uninstalled -c config/win64-mixed-msvc.cbc bootstrap
> before something else (in every case)

Bootstrap only needs to be called once. You may need to call it again
after updating Cerbero itself.

> or can I directly call
>> cerbero-uninstalled -c config/win64-mixed-msvc.cbc package gstreamer-1.0
> (because it is doing the bootstrap automatically here)?

No command will automatically run bootstrap for you.

> When building e.g. a 64 bit and a 32 version, do I need some kind of a
> clean?
> Or would a clean be even a bad thing, because in second build some steps can
> be skipped,
> because it was already built in first build?

64-bit and 32-bit versions are completely independent. They build
inside separate subdirs of the cerbero build directory.

> The meson 1.10 reports some errors. Are you interested to collect such
> errors?
> Here via email? Or in the bug-tracker?

I looked at the log in your email. The main issue seems to be that you
did not run a `clean` command when you switched branches to
meson-1.10. Please do that so that stale files built by the previous
Cerbero branch you were using are removed.

I was recently told by someone that they ran it all from scratch and
built both 32-bit and 64-bit successfully, and also used it in their
application, so it should work.

gstreamer-devel mailing list
gstreamer-devel at

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gstreamer-devel mailing list