Support Request #2274
closedQt Gui filter linker error
Description
Supportanfrage
During the updation of the Qt filter's CMake according to the new ADTF3.3.0 build framework, I am facing some linker errors. When the qt gui filter is compiled, the compiler is not able to find the object file(ex. Qt5Widgets-NOTFOUND object). This can be
seen when user selects project properties->Linker->Input->Additional dependencies. Here instead of the library path or the library itself, it shows Qt5Widgets-NOTFOUND and I have highlighted it in one of my attachments (my_filter_QT5WidgetLibError.PNG).
In order to cross verify, I have tried to build the qt demo filter delivered by the ADTF3.3.0, somehow the project builds but the “Qt5Widgets-NOTFOUND” is still found in the Additional dependencies. How could this be resolved in order to compile my filter without linker failure? I have tried changing the linking syntax (for ex: target_link_libraries(${TARGETNAME} PUBLIC adtf::ui Qt5::Widgets/Widgets/Qt5Widgets)) but none of them are working.
CMake version used : 3.10.1
Lösung
- QT_DIR-variable point to your own QT-Installation
- CMAKE_PREFIX_PATH also to QT
- Build Type must be RelWithDebInfo or Debug
Files
Updated by hidden almost 6 years ago
- Project changed from Public Support to 11
- Topic set to ADTF::Common
Updated by hidden almost 6 years ago
Hello Vinay,
thank you for your feedback.- Does your QT_DIR-variable point to your own QT-Installation (the delivered QT within the 3rdParty is just "for us". It is not for developing)?
Updated by hidden almost 6 years ago
Hello,
My Qt_DIR CMake variable points to my own local Qt installation directory.
Updated by hidden almost 6 years ago
- Status changed from New to Customer Feedback Required
Did you set the CMAKE_PREFIX_PATH also to QT ?
Please have a look at setups we made in the build_examples.bat
Updated by hidden almost 6 years ago
- Description updated (diff)
- Status changed from Customer Feedback Required to To Be Closed
- Resolution set to No Customer Feedback
No customer feedback, issue will be closed
Updated by hidden almost 6 years ago
- Project changed from 11 to Public Support
- Private changed from Yes to No