Re: Recommended dev setup?

[Pekka Paalanen]

On Sat, 3 Dec 2016 14:48:53 +1100
David Piper  wrote:

> I'll be pushing along in Ubuntu for now but I thought I should throw the
> question out here - what is the best dev loop for working with Wayland?
> Should I be using Ubuntu or should I look for an OS that supports Wayland
> out of the box? What kind of environment setup would make things faster?

I suppose the choice of OS/distribution makes most difference in how
easy it is to get all the dependencies of weston.

For working with Weston there are a few ways. If you work on a shell or
the core, you can run weston nested: it works on both X11 and Wayland
display servers. If you work on a specific backend, you obviously need
to use that backend. For working on direct-to-hardware backends like
DRM it will help a lot to have a second computer, since failures can
leave your local console unresponsive or broken.

If you want to work on weston-launch, then you'd need a system that
does not use logind, since the whole point of weston-launch is to offer
a fallback for systems not using logind.


Thanks,
pq


pgpmzRZlRFxiO.pgp
Description: OpenPGP digital signature
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Re: Recommended dev setup?

[Yong Bakos]

Hi David,

> On Dec 2, 2016, at 7:48 PM, David Piper  wrote:
> 
> Hi all,
> 
> I'm jumping back into the Wayland loop after more than a year. My first port 
> of call is once again building Wayland and Weston and getting some of the 
> sample clients running. About all I've done so far is install Weston the 
> quick and dirty (apt-get) way on Ubuntu and read through the build 
> instructions.
> 
> Next I'd like to follow the build instructions, get some of the sample 
> clients running and then start writing my own toy clients. Once I've done 
> that I wouldn't mind hacking a bit on the weston compositor - probably not 
> touching libweston itself, but at least getting to know it.
> 
> I'll be pushing along in Ubuntu for now but I thought I should throw the 
> question out here - what is the best dev loop for working with Wayland? 
> Should I be using Ubuntu or should I look for an OS that supports Wayland out 
> of the box? What kind of environment setup would make things faster?

Any major distro will be fine. Folks use Ubuntu, Fedora, etc.
You do not need to run a DE that uses Wayland in order to
build & run Wayland/Weston.

yong


> 
> Cheers,
> 
> David
> 
> ___
> wayland-devel mailing list
> wayland-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/wayland-devel

___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Recommended dev setup?

[David Piper]

Hi all,

I'm jumping back into the Wayland loop after more than a year. My first
port of call is once again building Wayland and Weston and getting some of
the sample clients running. About all I've done so far is install Weston
the quick and dirty (apt-get) way on Ubuntu and read through the build
instructions.

Next I'd like to follow the build instructions, get some of the sample
clients running and then start writing my own toy clients. Once I've done
that I wouldn't mind hacking a bit on the weston compositor - probably not
touching libweston itself, but at least getting to know it.

I'll be pushing along in Ubuntu for now but I thought I should throw the
question out here - what is the best dev loop for working with Wayland?
Should I be using Ubuntu or should I look for an OS that supports Wayland
out of the box? What kind of environment setup would make things faster?

Cheers,

David
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel