vcpkg support

[tzcnt]

Let's try to figure out how to get the TMC_IMPL requirement out of the vcpkg release.

[EvilMcStevil]

https://github.com/EvilMcStevil/vcpkg/tree/tmc

Here is an initial stab at a vcpkg port for toomanycooks and toomanycooks-asio,
It makes some CMakeLists.txt files which I personally think would be better off coming from the original project source itself, as then it would always be up to date. also.
It installs find_package hooks as unofficial-tmc as that is what vcpkg mandates when they are are not specified by the project itself.

Ideally a modification of hwloc in vcpkg would add the find_package integration, so we could just add find_package for that aswell. but if you supply that inside this repo, then the vcpkg port can easly override it.

[tzcnt]

Thank you. I will review this weekend and get back to you.

[tzcnt]

Wow, that's quite a bit more than I expected. I just finished the work to make header-only / all inline the default configuration. So a build file is not required any more. I'm working through the conanfile right now as it's a bit easier to manage.

Is there a way to allow the library consumer to specify the options here? https://www.fleetcode.com/oss/tmc/docs/dev/build_flags.html (note the added Build Modes section)

As well as make the dependency on tmc-asio / asio optional. I'd also remove the allocator requirement - this is just a suggestion, the user can pick any allocator they want.

[EvilMcStevil]

The majority of the files are just to make this a well behaved CMake project, as that is what vcpkg likes as a default.
ideally these would be supplied, in this repo,
( It doesn't stop it being header only, but it makes life really easy for users and packages to use it if they use cmake.)

The options can absolutely be specified, and they will end up in the generated CMake Targets generated at cmake install time.

So anybody linking the target will automatically use those options as they will end up in the interface.

configure_package_config_file(${CMAKE_CURRENT_SOURCE_DIR}/Config.cmake.in .......

at some point when I get around to it I will create a pull request on this repo with the CMakeLists.txt with all this included.

Oh, and the asio is optional in this example, there are 2 packages, one of which depends on the other. It may be nicer to have 1 package with options, but it was simpler this way because you have 2 git repos

[Akylzhan]

I think it is possible to make it as backward-cpp
They export INTERFACE library with backward.hpp header and OBJECT library with backward.hpp and backward.cpp for automatic stack trace printing on crash

[tzcnt]

Thanks - this is helpful. I like the way they did their conanfile integration as well.