Comment 5 for bug 1629749

The compiz-reloaded folks are maintaining a branch of Emerald which has
been ported to GTK3 and just had its last commit yesterday to fix some
GTK 3 deprecations. This is a currently maintained branch. Compiz-reloaded
itself is a branch of compiz 0.8.8 (which as of a month ago did not work with
GTK 3.22) but their Emerald package works just fine with upstream compiz
0.9.13, which is what I am using.

https://github.com/compiz-reloaded/emerald

On 10/23/2016 at 8:50 PM, "Cyril Brulebois" <email address hidden> wrote:
>
>Thanks for the Emerald tip, but I've been warned against it since
>it
>might be undermaintained.
>
>Another approach might be to look into libmarco, which seems to be
>a
>mate fork of libmetacity; I haven't looked into it yet though (but
>plan
>to if time permits).
>
>In the meanwhile, I've prepared a few patches against latest compiz
>trunk, so that compiz builds against Debian unstable. Pointers to
>the
>git repository and to the Debian packages for amd64 can be found
>here:
>https://compiz.alioth.debian.org/ — the patch series contains a
>workaround for this FTBFS by disabling libmetacity:
>https://anonscm.debian.org/cgit/compiz/compiz.git/commit/?h=unstabl
>e-v1&id=c36fa3cf661eb363f75ca54fe642bad0f0377f40
>
>I have only performed build tests for the time being, and made sure
>packages are installable.
>
>They're probably suboptimal since a bunch of things needed be
>disabled
>to build against Debian unstable, but the idea was to see whether
>we
>could bring back compiz to Debian, and then improve incrementally.
>
>--
>You received this bug notification because you are subscribed to
>the bug
>report.
>https://bugs.launchpad.net/bugs/1629749
>
>Title:
> window-decorator cannot build with libmetacity 3.22
>
>Status in Compiz:
> New
>
>Bug description:
> This is with compiz source
> compiz_0.9.13.0+16.10.20160818.2.orig.tar.gz
> build on Debian Unstable (not Ubuntu) and GTK 3.22 and Metacity
>3.22. Will become an issue for Ubuntu post-yakkety unless Ubuntu
>pins Metacity at version 3.20.
>
> Metacity/libmetacity 3.22 introduced radical changes that totally
> break compiz's gtk-window-decorator,which can neither build nor
>run
> against it. I played with it, a whole bunch of things compiz
>needed to
> link against were removed. This was the first error resulting
>from an
> attempt to build against Metacity 3.22:
>
> error: unknown type name ‘MetaButtonLayout’
> MetaButtonLayout button_layout;
>
>
> The possible killer for Metacity theme support:
>
>
>https://github.com/GNOME/metacity/commit/d7f2445ec7e70274c7501586a5
>37c699f6628335
> libmetacity: switch from .ssd to .csd
>
> and some of the changes probably behind breaking the build:
>
>
>https://github.com/GNOME/metacity/commit/2ee0ffbee0b52cb8fc3112906b
>ea1eaa737559f7
> libmetacity: don't expose MetaButton struct
>
>
>
>https://github.com/GNOME/metacity/commit/eee199e3b7ce87cbd08b4b6e4c
>9c55c804c6ff5f
> libmetacity: rename MetaButtonFunction to MetaButtonType
>
> Not sure a port to 3.22 would even still give the ability to read
> Metacity themes anyway, given the first commit listed above.
>
> Meanwhile, building gtk-window-decorator without metacity
>support at
> all was broken accidently in changes to support metacity 3.20 by
>using
> metacity version selectors but not checking to see if Metacity
>support
> is being used at all.
>
> I build compiz for use in Debian Unstable (and offer my builds
>for
> public use) so I saw this a couple days ago. All I could so was
>switch
> decorators to Emerald (which compiz-reloaded has ported to GTK3)
>and
> use the Emerald pixmap engine to write an Emerald theme matched
>to my
> metacity theme. Ubuntu MATE may have to do the same post-Yakkety
> unless Ubuntu either pins Metacity, gets a 3.22 port to work and
>finds
> it handles metacity themes, or modified gtk-window-decorator to
>read
> metacity themes directly without using libmetacity.
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/compiz/+bug/1629749/+subscriptions