| Summary: | Qt5 static will not build | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | fabrice nicol <fabrnicol> |
| Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | asturm |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge info and configure-step build | ||
Bug also shows up if using package.use instead of an inlined USE variable:
echo "dev-qt/qtcore static" >> /etc/portage/package.use/qtcore
Nope. $ emerge -vp qtcore These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-qt/qtcore-5.15.1:5/5.15.1::gentoo USE="icu -debug -old-kernel -systemd -test" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB @Andreas Sturmlechner OK, my mistake, I see static building is not supported for Qt5. This should be transformed into a request as it is quite useful for software deployment. In general we don't support that option. https://projects.gentoo.org/qa/policy-guide/installed-files.html#pg0302 OK, but "systemic" libraries like Qt5 are a special case. The security point of 0302 does not hold here: Qt group devs are numerous enough to handle that fine. And deploying 12 shared Qt5 libs has its own security implications for software deployment (e.g. version conflicts, hardening issues etc.). Static building is one domain in which Gentoo shines way brighter than other distros (except for Arch). There is case here. |
Created attachment 663115 [details] emerge info and configure-step build USE=static is supported by Qt5 ebuilds yet does not build into lib*Qt5*.a libraries