https://bugs.documentfoundation.org/show_bug.cgi?id=167571
--- Comment #2 from Klaus Kusche <[email protected]> --- (In reply to Eli Schwartz from comment #1) > (In reply to Klaus Kusche from comment #0) > > So please do not require any wayland dependencies for building LO > > > LO doesn't require any such thing! As already explained in the very Gentoo > bug you referenced, the Gentoo maintainer made this judgment call: "I am not > going to introduce an IUSE on LO that is invalid with !gtk[34] just to solve > that." As far as I understood that commit, the "I am not going to introduce an IUSE on LO that is invalid with !gtk[34] just to solve that." refers to a completely different problem: This commit completely *blocks* building LO on any big-endian platform, because big-endian platforms do not support gtk[wayland] at all, hence LO cannot depend on gtk[wayland] there, because there is no gtk[wayland]. I think this is completely irrelevant for little-endian platforms (like x86). > > and in prebuilt libreoffice downloads, do not assume > > that wayland-enabled runtime libraries for gtk3 or anything else are > > available! > > > This is illogical and nonsensical and not how computers work. Building LO > with *support* for users on Xorg and users on wayland means depending on a > gtk+[X,wayland]. > > It is not reasonable to demand upstream projects simply give the middle > finger to all wayland users. People installing upstream prebuilt binaries > have always needed to install library dependencies they don't strictly need > for a minimalist config. That's not what I said. Pre-building LO to support both platforms (i.e. to contain code for both X and wayland) is fine, I never argumented against that. But actually *starting* the pre-built LO download should be possible on a platform with no wayland at all (especially, non-wayland gkt libs). That's what I asked for: Do not assume that the runtime libs like gtk3 or mesa support wayland. LO may contain wayland code, but it should not require such libs for starting, it should only dynamically link to wayland functions after making sure that wayland is actually available and in use. And this is possible using dlopen or something similar, and it is common for large software systems with several backends. For example, if a server supports 5 different database backends, you don't need to install all 5 databases just to start the server and use a single database. (I didn't test, perhaps that already works fine?) Again: > Building LO > with *support* for users on Xorg and users on wayland means depending on a > gtk+[X,wayland]. Building: Yes, building it for both requires both being installed on the build platform. But custom-building it for just non-wayland should not require both on the build platform. Running: No, as explained above. So to make it clear again, I asked for two things: * Please allow LO to be custom-built without any wayland on the build system: Document what build options are needed to avoid wayland dependencies, what optional parts do not work without wayland and must be dropped, or whatever. * Allow prebuild LO binaries to start on systems without any piece of wayland software, even if they contain wayland code. Preferably also with the gtk backend (separating wayland from non-wayland gtk code should be possible), but at least with the non-gtk backends (skia, qt). -- You are receiving this mail because: You are the assignee for the bug.
