Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[package] jsonformoderncpp/all: cmake exported name is different than upstream
See original GitHub issueaccording to upstream: https://github.com/nlohmann/json#cmake
cmake should use nlohmann_json as target name.
conan index is using jsonformoderncpp and jsonformoderncpp::jsonformoderncpp
this should be fixed with e.g. self.cpp_info.name in the recipe
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
The upstream branch of your current branch does not match ...
This happens if the name of the upstream branch and local branch do not match, which sometimes happens, and usually is unwanted:
Read more >Simplify exporting of CMake Packages (#18634) · Issues
Exporting CMake packages currently requires some boilerplate that is error prone and hard to get right. As an effect, many projects are not ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
//@iceflowre
Ok, after some internal discussion we have decided to go with the copy instead of the renaming. This will allow keeping the recipe repo (this) consistent with the packages uploaded to the center and it will be easier to understand.