AFAIK this is effectively broken, since an ssh cert for mumbai.kapeli.com expired.
see this issue for more info: https://github.com/zealdocs/zeal/issues/1307
Git Clone URL: | https://aur.archlinux.org/zeal-git.git (read-only, click to copy) |
---|---|
Package Base: | zeal-git |
Description: | Offline documentation browser |
Upstream URL: | https://zealdocs.org/ |
Keywords: | api dash docs docset documentation offline |
Licenses: | GPL3 |
Conflicts: | zeal |
Provides: | zeal |
Submitter: | 5long |
Maintainer: | trollixx |
Last Packager: | trollixx |
Votes: | 81 |
Popularity: | 0.000201 |
First Submitted: | 2013-06-29 09:47 (UTC) |
Last Updated: | 2024-09-08 17:12 (UTC) |
AFAIK this is effectively broken, since an ssh cert for mumbai.kapeli.com expired.
see this issue for more info: https://github.com/zealdocs/zeal/issues/1307
Hi. I am using Manjaro Linux, and I am running into these errors:
unable to satisfy dependency 'lua53' required by lua-bit32
unable to satisfy dependency 'lua-bit32' required by sile-git
I could not find a lua53 package, but the lua package is at version 5.3.5-3.
@briangordon I just performed a clean build and it builds just fine.
I built both from the GitHub repo and from this AUR repo with makepkg -s
.
The issue must be on your end. Besides, latest commit was made on November 24th.
Doesn't build:
[62/66] Generating qrc_zeal.cpp
FAILED: src/app/qrc_zeal.cpp
cd /home/brian/.cache/yay/zeal-git/src/build/src/app && /usr/bin/rcc --name zeal --output /home/brian/.cache/yay/zeal-git/src/build/src/app/qrc_zeal.cpp /home/brian/.cache/yay/zeal-git/src/zeal/src/app/resources/zeal.qrc
RCC: Error in '/home/brian/.cache/yay/zeal-git/src/zeal/src/app/resources/zeal.qrc': Cannot find file 'zeal.ico'
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
Aborting...
Edit: Ah, looks like it is a problem on my end, with qt using a system call that's not whitelisted: https://stackoverflow.com/questions/51195528/rcc-error-in-resource-qrc-cannot-find-file-png
@trollixx I could be wrong but I think that's because ninja
has a more sensible default for the number of jobs used. On my six-core machine, it uses 8 parallel jobs (you can see this by running ninja --help
) so I'd guess it's two more than the number of available cores. make
on the other hand, doesn't use any sort of parallelism if no -j
option is passed.
I would guess that make
and ninja
would perform the same if passed the -j
flag with the same argument, but since this is an AUR package that's going to be used by other people, using ninja
seems a more logic choice instead of using make
and hard-coding the -j
flag.
@brainplot Done! Still uses Ninja, but now invokes cmake --build
and cmake --install
.
I am not sure if hard-coding Ninja is generally a good idea, but it does build much faster:
makepkg 10.03s user 3.08s system 181% cpu 7.217 total # ninja
makepkg 128.70s user 11.90s system 466% cpu 30.107 total # make
I ran rm -rf src/build *.tar.xz
before makepkg
to avoid fetching the code from GitHub.
@trollixx Thank you for the edit! I have a further suggestion. I know this is very commonly done across the AUR but I think that invoking the native build system directly kind of defeats the purpose of using CMake. Here's the PKGBUILD I was using.
This has the benefits of:
1) Not relying on whatever the default build system for CMake is. The previous version worked only because CMake uses make
by default; but that's been addressed now by specifying -G Ninja
explicitly.
2) Using the CMAKE_BUILD_PARALLEL_LEVEL
environment variable (if set by the user), which is used by CMake to spawn the specified number of jobs (equivalent to pass the -j <N>
flag.
@brainplot I've updated the build type to RelWithDebInfo, which I think is more appropriate for the pre-release packages.
Also switched to using Ninja instead of make, similarly to the community package.
Why doesn't the PKGBUILD have the -DCMAKE_BUILD_TYPE=Release
flag?
I downloaded the PKGBUILD and added it myself but it seems strange since the stable package in the main repos does have it!
Pinned Comments
trollixx commented on 2017-09-07 18:38 (UTC)