Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seamless integration with FetchContent #51

Merged
merged 2 commits into from
Sep 8, 2022

Commits on Sep 6, 2022

  1. CMake: Use project-specific paths

    When repa is included in a parent project via FetchContent,
    CMAKE_SOURCE_DIR and CMAKE_BINARY_DIR refer to the parent project,
    while PROJECT_SOURCE_DIR and PROJECT_BINARY_DIR still refer to repa.
    jngrad committed Sep 6, 2022
    Configuration menu
    Copy the full SHA
    d84b70b View commit details
    Browse the repository at this point in the history

Commits on Sep 7, 2022

  1. CMake: Use namespaced project options

    When repa is included in a parent project via FetchContent, the
    parent project options are inherited in the repa project, which
    can lead to name conflicts. For example, the parent project may
    want to build and run its own tests but none of the repa tests.
    jngrad committed Sep 7, 2022
    Configuration menu
    Copy the full SHA
    34cc834 View commit details
    Browse the repository at this point in the history