Skip to content

optional support (and boost configuration) issue #133

@jessey-git

Description

@jessey-git

This issue has 2 parts:

  • It appears as though the single-file, combined, CLI11.hpp file is built by first assembling the CLI/Optional.hpp file above the CLI/Version.hpp file. This has the side effect that some defines like CLI11_CPP17 won't be set yet when Optional.hpp starts looking over them.

  • There's no way to disable boost support. The library goes out of its way to detect boost but in my case I kind of don't want it to do that :) How do I ensure CLI11 doesn't drag in boost headers when I don't want it to? Maybe use an ALLOW_BOOST define that the user can set before including CLI11.hpp so the lib knows not to check at all.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions