Package Details: cpp-httplib-compiled 0.15.3-1

Git Clone URL: (read-only, click to copy)
Package Base: cpp-httplib-compiled
Description: A C++ HTTP/HTTPS server and client library (compiled version)
Upstream URL:
Keywords: networking requests
Licenses: MIT
Conflicts: cpp-httplib
Provides: cpp-httplib,
Submitter: sum01
Maintainer: sum01
Last Packager: sum01
Votes: 3
Popularity: 0.000104
First Submitted: 2020-05-29 03:12 (UTC)
Last Updated: 2024-02-06 17:56 (UTC)

Required by (5)

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

1 2 Next › Last »

sum01 commented on 2022-03-17 17:49 (UTC)

I looked into making it a split package, but since the header-only and compiled versions aren't using the same build I'm not sure it's worth doing. As far as I can tell, it would require anyone using the header-only package to still compile the whole thing, even though they don't need it.

Didn't realize having DESTDIR on the end vs front mattered, but I'll change that.

abouvier commented on 2022-02-25 00:02 (UTC) (edited on 2022-02-25 00:02 (UTC) by abouvier)

DESTDIR must be an environment variable to work with all cmake generators: DESTDIR="$pkgdir" cmake --build . --target install

abouvier commented on 2021-07-24 03:52 (UTC) (edited on 2021-07-24 04:26 (UTC) by abouvier)

You should make a split package to ease maintenance, because the source code and version are the same for both the header-only and compiled packages :p

abouvier commented on 2021-07-19 19:59 (UTC) (edited on 2021-07-19 20:36 (UTC) by abouvier)

Sorry, it's just me who finds the -compiled suffix ugly :p

Otherwise, could you add to provides=() [1] and set CMAKE_BUILD_TYPE to None [2]? :D



sum01 commented on 2021-07-19 18:02 (UTC)

@abouvier I'm not sure there's much benefit to renaming it now. libhttplib also seems a bit redundant. I believe the pinned comment is enough to explain the differences between the two (as well as what I have in the description).

See the previous conversation I had with FabioLolix about there not really being any "standard" way to go about something like this.

abouvier commented on 2021-07-19 01:21 (UTC)

And what do you think of the name libhttplib for the compiled version? :p

abouvier commented on 2021-07-16 04:48 (UTC) (edited on 2021-07-16 04:48 (UTC) by abouvier)

@sum01 Sorry I meant the public header interface of the library, not the full header-only library.

sum01 commented on 2021-07-16 04:20 (UTC)

@abouvier yes that's how I was using it. I suppose it could make sense to require them all, at least for the compiled version.

As for having both in the same package cpp-httplib, I don't think that would work, as the Cmake files vary based on if it was header-only or compiled. I could have it install only the compiled version's cmake files, but there are minor differences between them regardless (namely, it's aware it's header-only).

abouvier commented on 2021-07-16 03:05 (UTC) (edited on 2021-07-16 03:07 (UTC) by abouvier)

Are you using the optdepends array as an "optmakedepends"? It's not working because users need to manually install the required libraries before building the package.

I think you should build the library with every option enabled. Or create multiple packages for every possible combination of options :p

And I vote for the cpp-httplib package containing headers and shared lib ;)

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.