[bug] Major deviations from standard CMake Find Behaviour
See original GitHub issueEnvironment Details (include every applicable attribute)
- Operating System+version: Ubuntu 20.04
- Compiler+version: gcc9
- Conan version: 1.53
- Python version: 3.8
Steps to reproduce (Include if Applicable)
- Build Qt5 with conan
- Use e.g.
IF (NOT Qt5Core_FOUND) message(FATAL_ERROR "not found")
in your CMake code - Fail
Logs (Executed commands with output) (Include/Attach if Applicable)
not found
Issue Analytics
- State:
- Created a year ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
cmake_policy — CMake 3.25.1 Documentation
The CMake Policy mechanism is designed to help keep existing projects building as new versions of CMake introduce changes in behavior. Each new...
Read more >How to use c++20 modules with CMake? - Stack Overflow
I tried to compile using Clang with -std=c++2a -fmodules-ts and it says fatal error: module 'VulkanRender' not found. How can i tell clang...
Read more >The build system - Learn Netdata
The default behaviour in CMake is to search across predefined paths (e.g. CMAKE_LIBRARY_PATH ) that are based on heuristics about the ...
Read more >Quick CMake tutorial | CLion Documentation - JetBrains
1. Simple CMake project · Select File | New Project from the main menu. · Choose C++ Executable on the left-hand pane. ·...
Read more >Proper Release Versioning Goes a Long Way - Interrupt
Subscribe to get our latest posts straight to your mailbox. Table of Contents. Overview; Semantic Versioning. Incrementing MAJOR; Incrementing ...
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 FreeTop 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
Top GitHub Comments
After further investigation, you also miss the VERY important library type for your imported libraries! How should CMake know how to propagate dependencies transitively without that? It makes a huge difference if you are linking privately to a static library or a shared library.
Any idea how I could proceed without the “LOCATION” properties while you decide on/implement a fix? I.e. how can I find out in CMake where the library behind a corresponding target is located?