Hi, when trying to rebuild, I needed to pass --optimization 2 to meson configure. Due to -werror=true use in meson.build and this warn-error :
warning _FORTIFY_SOURCE requires compiling with optimization (-O)
Git Clone URL: | https://aur.archlinux.org/wlroots-git.git (read-only, click to copy) |
---|---|
Package Base: | wlroots-git |
Description: | Modular Wayland compositor library (git development version) |
Upstream URL: | https://gitlab.freedesktop.org/wlroots/wlroots |
Keywords: | compositor egl gles2 libdrm libinput library modular opengl vulkan wayland wlroots |
Licenses: | MIT |
Provides: | libwlroots-0.19.so |
Submitter: | aperez |
Maintainer: | aperez (GreyXor) |
Last Packager: | GreyXor |
Votes: | 65 |
Popularity: | 1.50 |
First Submitted: | 2018-02-20 16:48 (UTC) |
Last Updated: | 2024-07-14 10:33 (UTC) |
« First ‹ Previous 1 .. 7 8 9 10 11 12 13 Next › Last »
Hi, when trying to rebuild, I needed to pass --optimization 2 to meson configure. Due to -werror=true use in meson.build and this warn-error :
warning _FORTIFY_SOURCE requires compiling with optimization (-O)
When building in a clean chroot like so:
makechrootpkg -c -r $BUILD_CHROOT -I ../scdoc/scdoc-1.5.2-2-any.pkg.tar.xz -I ../dummy-opengl-driver-git/dummy-opengl-driver-git-1-3-any.pkg.tar.xz -I ../xcb-util-errors/xcb-util-errors-1.0-1-x86_64.pkg.tar.xz
If fails with:
Dependency egl found: NO (tried pkgconfig) meson.build:57:0: ERROR: Dependency "egl" not found, tried pkgconfig
I think the 'opengl-driver' dependency should be replaced with 'mesa', as it provides opengl-driver and probably lots of GL stuff. But as I'm a novice, I'm really not sure.
When replacing 'opengl-driver' with 'mesa' though it build correctly with this command:
makechrootpkg -c -r $BUILD_CHROOT -I ../scdoc/scdoc-1.5.2-2-any.pkg.tar.xz -I ../xcb-util-errors/xcb-util-errors-1.0-1-x86_64.pkg.tar.xz
PS: How can I format text as a code block?
@linkmauve: Unfortunately, reusing the build directory with Meson has a huge issue: when updating Meson, the new version may be incompatible with build directories generated using older versions of Meson, and AFAIK it is not possible to determine when the directory needs to be re-created. That's the reason why the directory is always deleted. If you know some way to know when the build directory needs to be thrown away and re-created, I would be interested in knowing! :)
Hi, please apply this patch to keep the build directory between builds: https://linkmauve.fr/files/0001-Move-meson-call-to-prepare-to-keep-the-build-directo.patch
IMPORTANT
Please do not flag this package as out-of-date if the only change you need is to update to a newer version. It is not needed because it always fetches the sources using Git and uses the most recent version without needing to modify the PKGBUILD — just rebuild the package.
Also, please try building in a clean chroot before assuming that the PKGBUILD is broken.
@aperez: Sure, no problem. I wasn't sure how big rootston was, or how long it took to compile. If it's small, then I'm sure it's fine.
@InfernoZeus: Updated, thanks a lot for the heads up. As for rootston
, I would rather leave it as part of this package. It's small enough as to not make practically any difference...
The PKGBUILD needs to be updated after the recent changes to the Meson build options. I've used these:
meson build \
--prefix /usr \
--buildtype debug \
-Dlibcap=enabled \
-Dlogind=enabled \
-Dlogind-provider=systemd \
-Dxwayland=enabled \
-Dx11-backend=enabled \
-Dxcb-errors=enabled \
-Drootston=true \
-Dexamples=false
I tried setting rootston to false, but the install step expects it to be built. Perhaps rootston should be moved to its own package?
I think you should include pixman as a dependency.
@thx1138: Thanks for the suggestion, I have pushed a new version which installs rootston and its example configuration file.
Pinned Comments
aperez commented on 2018-09-28 08:31 (UTC) (edited on 2019-03-07 16:25 (UTC) by aperez)
IMPORTANT
Please do not flag this package as out-of-date if the only change you need is to update to a newer version. It is not needed because it always fetches the sources using Git and uses the most recent version without needing to modify the PKGBUILD — just rebuild the package.
Also, please try building in a clean chroot before assuming that the PKGBUILD is broken.