On Wed, 14 Oct 2015 22:21:31 -0700 Bill Spitzak <spit...@gmail.com> wrote:
> It seems like /usr/bin/Xwayland is hard-coded into xwayland.so. This > makes it not run local installed versions of Xwayland. I could not get X > programs to work under wayland without doing "sudo ln -s > ~/install/bin/Xwayland /usr/bin". > > I noticed this because I had no /usr/bin/Xwayland, but I am concerned > that if it really is installed, a developer will not realize they are > not running their locally installed copy. > > There is a configure option --with-xserver-path but it would help if > --prefix worked as a default (ie $prefix/bin/Xwayland). That would be a wrong default for me now, while it would have been the right default earlier this year. Either way, someone loses. That's why there is --with-xserver-path. > Another possible solution is to use an environment variable ($XWAYLAND > maybe?) as the name of the program. > > Maybe a better question is why the path is hard-coded, rather than it > searching the path for this? There is also a weston.ini option for the Xwayland path, see 'man weston.ini'. Thanks, pq
pgpPGTlhkqgFR.pgp
Description: OpenPGP digital signature
_______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
