Are you saying that if I make $PREFIX/etc/X11/xorg.conf.d/foo and put my
config in there, xwayland will read it? And it will then ignore the
xorg.conf?
I still do not see this solving the real problem however. The normal
Xorg will follow the exact same rules, so if xwayland is compiled
without $PREFIX then it is impossible to use this to make xwayland and
normal Xorg see different config files. Even with $PREFIX this does not
allow xwayland to see "no" config file, as the missing file will make it
still fall back to searching everywhere and it will find the xorg.conf
file that I do not want it to see.
So I still feel that my solution of changing the conf file name is the
only thing that will work. We can put it in xorg.conf.d if that makes
some kind of sense (though I completely do not understand the purpose of
this).
Pekka Paalanen wrote:
On Tue, 04 Sep 2012 12:00:09 -0700
Bill Spitzak <[email protected]> wrote:
However I then realized that changing the search path would not fix any
xwayland because a "real" installation would not have a $PREFIX anyway,
so there had to be a different method to give wayland a different .conf
file. So at that point I switched to using a different name for the
.conf file.
I don't know if there are other conflicting files in xorg.conf.d. If so
they may need renaming for the wayland version too.
The whole point of xorg.conf.d is that files can have any names, and
they all will be read in in alphabetical order. Maybe they need a .conf
suffix or not, don't know. If you are changing names, you would have to
change the name of the directory.
Thanks,
pq
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
