Skip to content

Make Optional26 Packageable #28

@bretbrownjr

Description

@bretbrownjr

I attempted to add Optional26 to the Conan local recipe index I am finishing up in bemanproject/beman#21.

Two problems (so far):

  • Optional26 needs tarball and/or zip releases.
  • Optional26 uses CMakeLists.txt that assumes dependencies, at least googletest are vendored into the repo via git submodule workflows

The first issue can be fairly trivially resolved by clicking using the release feature in the github.com web UI and cutting a release. Of course, an established process and even CI for this task would be great, including developing patterns and CI scripts that other beman projects could benefit from.

The second issue could be a matter of making the relevant add_subdirectory conditional somehow, using find_package workflows instead and adding googletest as a package dependency in Conan to ensure it's available to build against. It's also possible that using FetchContent instead of git-submodules would make the packaging "work", but Conan is designed such that it does source code indexing and fetching, so I would prefer to adhere to that design when using Conan.

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