Re: [Capy review] On peer dependencies
Ruben Perez via Boost <[email protected]> Tue, 23 Jun 2026 19:26:04 +0200
| Newsgroups | gmane.comp.lib.boost.devel |
|---|---|
| Message-ID | <CACR-md+8JmFFAjmRBS_ARvKmQGo_EnXMiNLV2Nzb+bf2VkN6mg@mail.gmail.com> |
>> Asio is included in an optional header (capy/buffers/asio.hpp) to facilitate integration. > > > I would prefer if this was > > #include <capy/asio/asio.hpp> > > And then the repository directory include/boost/capy/asio was added to an "ignore" or "optional" list that Boostdep could understand. > > Thanks > To add data points here, this same thing happens with: * Asio and Boost.Context (via asio/spawn.hpp) * MySQL and Boost.Pfr (via mysql/pfr.hpp) The only problem with an "ignore directory" is that these components may have an implementation header counterpart (mysql/impl/pfr.hpp). Best, Ruben. _______________________________________________ Boost mailing list -- [email protected] To unsubscribe send an email to [email protected] https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/[email protected]/message/VQNQZSOWQK5IPLWLYAOBB2TMJI525NSD/