There are different pkgrel
in .SRCINFO and PKGBUILD:
https://aur.archlinux.org/cgit/aur.git/commit/?h=folly&id=266e859d579e86fef920c0ee7b4fd2aae6f3cc44
This causes yay to reinstall folly on every update.
Git Clone URL: | https://aur.archlinux.org/folly.git (read-only, click to copy) |
---|---|
Package Base: | folly |
Description: | An open-source C++ library developed and used at Facebook |
Upstream URL: | https://github.com/facebook/folly |
Licenses: | Apache-2.0 |
Provides: | libfolly.so, libfollybenchmark.so, libfolly_test_util.so |
Submitter: | dseg |
Maintainer: | ftiasch (MrAnno, carsme) |
Last Packager: | ftiasch |
Votes: | 7 |
Popularity: | 0.000015 |
First Submitted: | 2015-03-20 08:29 (UTC) |
Last Updated: | 2025-06-04 04:44 (UTC) |
There are different pkgrel
in .SRCINFO and PKGBUILD:
https://aur.archlinux.org/cgit/aur.git/commit/?h=folly&id=266e859d579e86fef920c0ee7b4fd2aae6f3cc44
This causes yay to reinstall folly on every update.
Some new depends or possibly optdepends seem to be libaio, libunwind, libdwarf, and liburing.
getting a build error with fizz and wangle related to folly
CMake Error in CMakeLists.txt:
Imported target "Folly::folly" includes non-existent path
"/include"
in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include:
-
The path was deleted, renamed, or moved to another location.
-
An install or uninstall procedure did not complete successfully.
The installation package was faulty and references files it does not
provide.
Waiting for https://github.com/facebook/folly/pull/1439 to be released.
@MrAnno, https://github.com/facebook/folly/pull/1433 got merged this morning. Hopefully that fixes the issue.
@dxu Yeah, #1433 contains a workaround for CMake < 3.19 too. (The CMake v3.19 release is expected in October.)
Getting following configure error:
CMake Error at CMakeLists.txt:439 (file):
Error evaluating generator expression:
$<COMPILE_LANG_AND_ID:CUDA,NVIDIA>
$<COMPILE_LANG_AND_ID:lang,id> may only be used with binary targets to
specify include directories, compile definitions, and compile options. It
may not be used with the add_custom_command, add_custom_target, or
file(GENERATE) commands.
https://github.com/facebook/folly/pull/1433 seems like it'll fix the issue but I haven't tried it out.
I ran into issues because I have specified the SRCDEST for makepkg. The source name for folly, fizz and wangle is just the version, e.g.: v2020.02.03.00.tar.gz and when running makepkg, it skips the download step and fails verifying it with sha256sum. Could you maybe prefix the files with their corresponding name? Thanks in advance :)!
Pinned Comments
carsme commented on 2023-12-07 04:02 (UTC)
BREAKING CHANGE: This package now builds shared objects:
instead of the static libraries:
Downstream packages must move
folly
from themakedepends
todepends
array to stay functional.We are doing this change since dynamic rather than static linking between packages is more in line with Arch Linux packaging practices (or just Linux packaging practices in general).