Skip to content

Build fails to find capy folder unless capy is cloned in a neighbouring folder #178

Description

@ja11sop

Running (for a standalone build):

cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release

from the corosio folder after cloning (per the build instructions) fails with errors:

-- Fetching capy...
-- Could NOT find WolfSSL (missing: WolfSSL_INCLUDE_DIR WolfSSL_LIBRARY) 
CMake Error at test/unit/CMakeLists.txt:11 (add_subdirectory):
  add_subdirectory given source "../../../capy/extra/test_suite" which is not
  an existing directory.
...
CMake Error at test/unit/CMakeLists.txt:44 (boost_capy_test_suite_discover_tests):
  Unknown CMake command "boost_capy_test_suite_discover_tests".
...
-- Configuring incomplete, errors occurred!

This works if you happen to have capy cloned into a neighbouring folder like this:

cppalliance (example)
├── capy
└── corosio

which masks the error.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions