'make check' should not require 'make install' first. Add some sort of tests, that ensure all files are loaded from the build directory, and nothing is accidentally loaded from the system, including: weston.ini, weston plugins, backends, helper programs (weston-desktop-shell, weston-keyboard, etc.). We want to notice if anything gets used from the system, because that compromises the test results. There could still be some cases where some components might be picked up from the system. All those need to be fixed. Maybe we should have a some sort of switch to Weston to put it into test mode, which makes it skip all normal search paths? http://cgit.freedesktop.org/wayland/weston/commit/?id=c7210434d45cff0135e42bd3047988e1274d49dd was a good step in that direction. Is it enough? Are there any security implications?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/weston/issues/51.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.