using the library fails on cmake step with missing config (e.g. up_cppConfig.cmake)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cmake, cpp
- Domain
- build-system
Research direction
Start with the reported conan commands and the generated CMakeLists.txt, especially the find_package call that fails for up_cpp. Reproduce the installation and create steps, then inspect the resulting build and package configuration files. Done means a documented or verified setup where the example project can locate up_cppConfig.cmake.
Written by the indexing model from the issue text.
Description
steps e.g.
conan new cmake_exe -d name=ue_can_prj -d version=0.1 -d requires=up-cpp/1.0.1
conan install . --output-folder=build --build=missing
"conan create ."
error:
-------------------------8<------------------------
CMake Error at CMakeLists.txt:4 (find_package):
Could not find a package configuration file provided by "up_cpp" with any
of the following names:
up_cppConfig.cmake
up_cpp-config.cmake
Add the installation prefix of "up_cpp" to CMAKE_PREFIX_PATH or set
"up_cpp_DIR" to a directory containing one of the above files. If "up_cpp"
provides a separate development package or SDK, be sure it has been
installed.
-------------------------8<------------------------
How can I solve this, or what is the suggested way to setup a project using up_cpp?
Thanks
- Dominant language
- C++
- Stars
- 29
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from eclipse-uprotocol/up-cpp
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
eclipse-uprotocol/up-cpp#327 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
eclipse-uprotocol/up-cpp#320 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
eclipse-uprotocol/up-cpp#319 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
eclipse-uprotocol/up-cpp#303 ·
-
enhancement help wanted quality
Difficulty 3/5 1-2 days Newbie friendliness 45/100
eclipse-uprotocol/up-cpp#300 · 1 comment ·
All issues in eclipse-uprotocol/up-cpp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
hipRTC lit tests compile against /opt/rocm's LLVM instead of the ROCm under test (ci/ hardcodes LLVM_PATH)Possibly taken @bernardogv claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
請增加教學：數字後的句號Open
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day