[boost-*] Header-only support about vcpkg

[Neumann-A]

Mostly header-only, library compilation is required for few features.

I don't see why vcpkg should support something upstream does not actively support.

[Zitrax]

Mostly header-only, library compilation is required for few features.

I don't see why vcpkg should support something upstream does not actively support.

On the other hand it feels like it should be possible to use header only mode for libraries that support it without being forced to build it.

For example it looks like Conan support this with an option boost:header_only=True, doesn't sound unreasonable to me that vcpkg could offer something similar.

[Kojoley]

Mostly header-only, library compilation is required for few features.

I don't see why vcpkg should support something upstream does not actively support.

There are some libraries that explicitly support both header-only and compiled library. (I think Beast, Regex)

Threads support can be disabled via threading=single, I don't know how well it is tested though.

[Zitrax]

Threads support can be disabled via threading=single, I don't know how well it is tested though.

But is there a way to pass that to the boost vcpkg ports without adding your own overlay?

[github-actions]

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

[Zitrax]

Ping.