Package Details: cpp-httplib-compiled 0.18.1-1

Git Clone URL: https://aur.archlinux.org/cpp-httplib-compiled.git (read-only, click to copy)
Package Base: cpp-httplib-compiled
Description: A C++ HTTP/HTTPS server and client library (compiled version)
Upstream URL: https://github.com/yhirose/cpp-httplib
Keywords: networking requests
Licenses: MIT
Conflicts: cpp-httplib
Provides: cpp-httplib, libcpp-httplib.so
Submitter: sum01
Maintainer: sum01
Last Packager: sum01
Votes: 4
Popularity: 0.26
First Submitted: 2020-05-29 03:12 (UTC)
Last Updated: 2024-10-19 02:56 (UTC)

Required by (4)

Sources (1)

Pinned Comments

sum01 commented on 2021-04-23 19:40 (UTC)

@Spixmaster so cpp-httplib is header-only, and must be compiled in any project you use it in. cpp-httplib-compiled splits the header into an interface (header) and implementation, allowing you to just link against it. Lets you avoid having to compile it every time.

Latest Comments

« First ‹ Previous 1 2

sum01 commented on 2021-05-17 19:19 (UTC)

There are header-only packages in official with no -header suffix. Considering header-only is the default in upstream, and there's no real rule for this, I think I'll leave it as-is.

FabioLolix commented on 2021-05-17 17:09 (UTC)

Honestly I can't point to a wiki page, but all programs are shipped compiled by default and headers only packages have the -headers suffix headers compiled

About pkgbuilds name, it can't be changed. You can upload cpp-httplib-header and submit a merge request of cpp-httplib into it and later upload my revision of cpp-httplib and submit a merge request of cpp-httplib-compiled into it, so votes, comments and notification are preserved for the 'same scope' pkgbuilds

sum01 commented on 2021-05-17 16:48 (UTC)

@FabioLolix is that an AUR packaging rule? I looked when I originally created these but couldn't find anything to go by. The reason I went with the "normal" package (cpp-httplib) as the header-only version is because it's the default state of the upstream, and compilation is an alternate method that's available.

Also, I thought I can't just change the name in the PKGBUILD since a TU has to do something?

FabioLolix commented on 2021-05-17 16:33 (UTC)

Hello, this pkgbuild need to be called simply 'cpp-httplib' instead of 'cpp-httplib-compiled' since in Arch packaging is normal to ship binary, libraries and headers in the same package, while what is now 'cpp-httplib' need to be renamed 'cpp-httplib-header'

Please rename sources in a way to be 'reusable', since both cpp-httplib pkgbuild use the same sources

I have revisioned both pkgbuilds (I have also removed some not necessary things [zlib is always installed])

Spixmaster commented on 2021-04-24 11:23 (UTC) (edited on 2021-04-24 11:24 (UTC) by Spixmaster)

@sum01 I understand. The two packages just have different compile options. In this case, "-bin" is not suitable.

sum01 commented on 2021-04-23 19:40 (UTC)

@Spixmaster so cpp-httplib is header-only, and must be compiled in any project you use it in. cpp-httplib-compiled splits the header into an interface (header) and implementation, allowing you to just link against it. Lets you avoid having to compile it every time.

Spixmaster commented on 2021-04-23 18:51 (UTC)

@sum01 I looked at both PKGBUILDs and do not exactly know the difference between both. I ask myself what even needs to be compiled as it is header only.

sum01 commented on 2021-04-23 15:24 (UTC)

@Spixmaster I though -bin was only for pre-compiled packages? This is still being compiled when you build it, so I assumed the -bin didn't apply when I was naming it.

Spixmaster commented on 2021-04-23 13:34 (UTC)

The AUR convention for a compiled version would be "cpp-httplib-bin".

« First ‹ Previous 1 2