Summary: | Allow building inside a container | ||
---|---|---|---|
Product: | Wayland | Reporter: | Krasi <krasi.root> |
Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED NOTOURBUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | peter.hutterer |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Krasi
2018-01-14 21:33:41 UTC
Looks like your include paths are messed up because it can't find the header files for any of the external packages (libevdev, libudev, and mtdev). This is either some local issue with a messed up include path or a meson issue where it gets past the meson stage but ninja then fails to pick up the includes. Did you read the top of my message? In other words , how can I compile on one machine or inside a container and do the installation on another? Is the installation just a matter of copying some files? ninja install has a dependency on ninja build (or whatever the build target is called). So if the timestamps change or any of the headers, or any of the dependencies, it'll rebuild. basically: if you change anything underneath ninja, it'll rebuild.
distributions do what you want to do with chroots, etc. e.g. if you're on fedora you're probably better off with mock than docker containers.
> Is the installation just a matter of copying some files?
basically yes. I think there's a restorecon in there too but that may not be needed on your distro.
You can also run 'DESTDIR=/path/to/fake-root-dir/ ninja -C build install' inside the container. This will install everything as if $DESTDIR were the root, allowing you to install there as an unprivileged user in the container, and copy the files out from the host. |
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.