Hi guys,
On 25 July 2017 at 11:39, Jonas Ådahl wrote:
> Add a --visibility flag that enables the user to tweak the visibility
> of the symbols generated by wayland-scanner. Three alternatives are
> exposed:
>
> 'export': as has always been done up until now, export the symbols
> using WL_EXPORT,
On Wed, 26 Jul 2017 15:49:57 +0800
Jonas Ådahl wrote:
> On Tue, Jul 25, 2017 at 02:44:29PM +0300, Pekka Paalanen wrote:
> > On Tue, 25 Jul 2017 18:39:56 +0800
> > Jonas Ådahl wrote:
> >
> > > Add a --visibility flag that enables the user to tweak the visibility
> > > of the symbols generated
On Tue, Jul 25, 2017 at 02:44:29PM +0300, Pekka Paalanen wrote:
> On Tue, 25 Jul 2017 18:39:56 +0800
> Jonas Ådahl wrote:
>
> > Add a --visibility flag that enables the user to tweak the visibility
> > of the symbols generated by wayland-scanner. Three alternatives are
> > exposed:
> >
> > 'expo
On Tue, 25 Jul 2017 14:44:29 +0300
Pekka Paalanen wrote:
> On Tue, 25 Jul 2017 18:39:56 +0800
> Jonas Ådahl wrote:
>
> > Add a --visibility flag that enables the user to tweak the visibility
> > of the symbols generated by wayland-scanner. Three alternatives are
> > exposed:
> >
> > 'export':
On Tue, 25 Jul 2017 18:39:56 +0800
Jonas Ådahl wrote:
> Add a --visibility flag that enables the user to tweak the visibility
> of the symbols generated by wayland-scanner. Three alternatives are
> exposed:
>
> 'export': as has always been done up until now, export the symbols
> using WL_EXPORT,
Add a --visibility flag that enables the user to tweak the visibility
of the symbols generated by wayland-scanner. Three alternatives are
exposed:
'export': as has always been done up until now, export the symbols
using WL_EXPORT, making making them exposed externally. This is the
default in order
