I'd like to see Coolians suggestion in this PKGBUILD, but not all available cores should be used, because when I tried that (luckily only) my terminal emulator died.
Maybe something like this $(($(nproc) * 3 / 4))
(this will break with one core available because it then returns 0
) or $(nproc --ignore 2)
(this will always atleast return 1) could be used instead.
Pinned Comments
Scrumplex commented on 2023-12-02 12:39 (UTC)
Options like
-j $(nproc)
are supposed to be set by your local makepkg.conf.Please read https://wiki.archlinux.org/title/Makepkg#Parallel_compilation
g3tchoo commented on 2023-11-06 16:38 (UTC) (edited on 2023-11-06 16:38 (UTC) by g3tchoo)
following some feedback and reports of issues, i think we're going to stick with
jdk17-openjdk
for now. while user choice is important, i believe there needs to be a balance between that and reliably building this package without manual intervention. this is also why thedepends
array will still containjava-runtime
rather than any specific jdk - since unlike building prism, we don't need to know the path of the jdk to ensure things work as expected.to ensure you don't still have
jdk17-openjdk
after building (and you don't use it), you can tell makepkg to remove unneededmakedepends
when it's done:if you have already built prismlauncher, you can also run one of the following commands:
for those facing further issues with dependencies in the future, i would also recommend using chroot builds. these allow aur packages to build in isolated and more reproducible environments, which can commonly fix these types of issues. the
devtools
package provides a script namedextra-x86_64-build
that can be used in place of makepkg to do this easily. building prismlauncher with this can be done like so: