Search Criteria
Package Details: msquic-git 2.3.0.r105.g6abfbec41-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/msquic-git.git (read-only, click to copy) |
---|---|
Package Base: | msquic-git |
Description: | Microsoft implementation of the IETF QUIC protocol |
Upstream URL: | https://github.com/microsoft/msquic |
Licenses: | MIT |
Conflicts: | libmsquic.so, msquic |
Provides: | libmsquic.so, msquic |
Submitter: | fmauNeko |
Maintainer: | FabioLolix (Gigas002) |
Last Packager: | FabioLolix |
Votes: | 1 |
Popularity: | 0.000000 |
First Submitted: | 2021-11-09 08:52 (UTC) |
Last Updated: | 2024-04-09 13:38 (UTC) |
Dependencies (4)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- numactl (numactl-gitAUR)
- cmake (cmake-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
Required by (1)
- dotnet-runtime-preview-bin (requires msquic) (optional)
Latest Comments
FabioLolix commented on 2023-12-22 14:34 (UTC)
Different thing, it don't like the system's version because it too new
Gigas002 commented on 2023-12-22 14:33 (UTC) (edited on 2023-12-22 14:33 (UTC) by Gigas002)
AFAIK it's hardcode was fixed with 7ea0e2e640008ad5c86d8d31e0cd186399b6b404, or are we talking about different things? Current submodule's
openssl
fork uses3.1.4
version.FabioLolix commented on 2023-12-21 08:41 (UTC)
Hello Gigas, this is FabioLolix not fmauNeko, I have worked on the pkgbuilds yesterday, almost ready just one more day of patience. Ok to use openssl3 but it fail to use the system version because it is hardcode to v3.0 while there v3.2 on Arch, also tests don't work for the git version
Gigas002 commented on 2023-12-20 13:41 (UTC)
@fmauNeko thanks! I'm thinking about raising the minimal supported version of
openssl
to3.0.0
and adding the-DQUIC_TLS='openssl3'
(to force usage of bundledopenssl3
instead ofopenssl11
) and-DQUIC_USE_SYSTEM_LIBCRYPTO='on'
(to use system-wide installation ofopenssl
'slibcrypto
) cmake flags. Also the currentcmake_args.patch
doesn't seem to be a requirements, since package is usable perfectly well without it. Don't know all of the use-cases of this library, but my .NET server with HTTP/3 works perfectly well with these changes. Do you approve these?FabioLolix commented on 2023-12-20 11:41 (UTC)
@Gigas002 added you as co-maintainer
Gigas002 commented on 2023-12-20 11:28 (UTC)
@fmauNeko can I adopt this repo if you're not interested in it?