Hey

Nope not yet. Will try it, just need to learn it :- )

It does look like a similar issue. I was able to find a workaround thanks to this bug report. Setting the target OSX version to 10.12 in CMake did the trick.

@Joachim-W Do you have c:\Qt\5.11.1\mingw53_32\lib\cmake\Qt5Gui (adapt the path to the Qt version you installed) and if so iis there anything inside?

I am curious on how the clarification will evolve for the topic “Describing build components for CMake support with Qt”.

Thanks for the feedback, I opened Bug #71354.

2nd UPDATE:

Problem was by natural source. The light reflects from window into camera.
2nd problem was using file as buffer.

I solved it by using grab image from QCameraViewFinder widget and send by memory.

Hi and welcome to devnet,

Because it's complex to integrate one build system with another. What 3rd party is it ?

I know this is an old topic. But I stumbled upon this topic multiple times, but now I got CMake in QtCreator with Visual Studio 15 2017 working. But had to change a few things.

In the Qt kit, I choose:
CMake Generator
Generator: Visual Studio 15 2017 Win 64.
Extra generator: None
Platform: empty
Toolset: empty

CMake Configuration: only CMAKE_PREFIX_PATH:STRING=%{QT:QT_INSTALL_PREFIX}, removed the others

When generating a cmake project, I have to change the resulting Build Settings (for each build configuration).

CMAKE_BUILD_TYPE: Debug
CMAKE_CONFIGURATION_TYPES: Debug

Build steps: choose "ALL_BUILD" instead of "all"

For us this resulted in a working build using msbuild, which allows us to build Wix installers etc. as well, something that cannot be done with NMake Makefiles.

@Toprakete said in CMake cannot find some 3D modules (3DRender, 3DExtras):

Qt3DRender

Hi and welcome to devnet,

I would check what include paths you have gathered to see if they indeed point to your Qt 5.11.2 installation.

Hi and welcome to devnet,

You should take a look at the various IPC options provided by Qt.

@ambershark oki, i appreciate your attention

Okay, I've just seen in the Building for android page that at most NDK r10 must be used. I recompiled qt with it and targeting android-21 platform. It works with QMake but with CMake I still get the same error though. Quite a step ahead fortunately :)

Hello,

Sorry for the novice mistake! I was trying to use different compilers in the NDK but i end up with the same error. The code i uploaded before was from one of my trials.
I did change my configuration to x86 but i still get the same error. Since this is my 1st time for android, I may have missed something.

The error stays the same. The 1st few line of my cmake error log states:

Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed. Compiler: /home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/i686-linux-android-g++ Build flags: Id flags: The output was: 1 /home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/i686-linux-android/4.9.x/../../../../i686-linux-android/bin/ld: error: cannot open crtbegin_dynamic.o: No such file or directory /home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/i686-linux-android/4.9.x/../../../../i686-linux-android/bin/ld: error: cannot open crtend_android.o: No such file or directory /home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/i686-linux-android/4.9.x/../../../../i686-linux-android/bin/ld: error: cannot find -lstdc++ /home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/i686-linux-android/4.9.x/../../../../i686-linux-android/bin/ld: error: cannot find -lm /home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/i686-linux-android/4.9.x/../../../../i686-linux-android/bin/ld: error: cannot find -lc /home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/i686-linux-android/4.9.x/../../../../i686-linux-android/bin/ld: error: cannot find -ldl collect2: error: ld returned 1 exit status

and the cmake output states

-- The CXX compiler identification is GNU 4.9.0 -- Check for working CXX compiler: /home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/i686-linux-android-gcc -- Check for working CXX compiler: /home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/i686-linux-android-gcc -- broken CMake Error at /usr/share/cmake-3.5/Modules/CMakeTestCXXCompiler.cmake:54 (message): The C++ compiler "/home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/i686-linux-android-gcc" is not able to compile a simple test program. It fails with the following output: Change Dir: /home/user/testProjects/build-bubbleWork-Android_for_x86_GCC_4_9_Qt_5_9_3_for_Android_x86-Default/CMakeFiles/CMakeTmp Run Build Command:"/usr/bin/make" "cmTC_c05c5/fast" /usr/bin/make -f CMakeFiles/cmTC_c05c5.dir/build.make CMakeFiles/cmTC_c05c5.dir/build make[1]: Entering directory '/home/user/testProjects/build-bubbleWork-Android_for_x86_GCC_4_9_Qt_5_9_3_for_Android_x86-Default/CMakeFiles/CMakeTmp' Building CXX object CMakeFiles/cmTC_c05c5.dir/testCXXCompiler.cxx.o /home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/i686-linux-android-gcc -o CMakeFiles/cmTC_c05c5.dir/testCXXCompiler.cxx.o -c /home/user/testProjects/build-bubbleWork-Android_for_x86_GCC_4_9_Qt_5_9_3_for_Android_x86-Default/CMakeFiles/CMakeTmp/testCXXCompiler.cxx Linking CXX executable cmTC_c05c5 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_c05c5.dir/link.txt --verbose=1 /home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/i686-linux-android-gcc CMakeFiles/cmTC_c05c5.dir/testCXXCompiler.cxx.o -o cmTC_c05c5 -rdynamic /home/user/android-ndk-r16b/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/i686-linux-android/4.9.x/../../../../i686-linux-android/bin/ld: error: cannot open crtbegin_dynamic.o: No such file or directory

@Valveware said in Promoting to custom widget in QtDesigner '*.hpp' no such file or directory [cmake]:

file(GLOB_RECURSE QT_MOC RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} FOLLOW_SYMLINKS include/dashboard/*.hpp)

Ok that looks like it would indeed moc your cameraframe.hpp.. So that's probably not the issue.

Can you share the build log from gcc? And also the ui_main_window.h file as well as ui_cameraframe.h?

@SGaist thanks!

I heard opposing arguments to that when it comes to moc/rcc/uic. Personally, I use the set(CMAKE_AUTOMOC ON) way

Hey , i just asked in repo and they said "they have not enabled d3d in project" , so i guess i will stick to Linux for this one

Hi...
i see vtable error link library error...
i solved to create a normal file.pro...
other way i must create a extra cmake file compatible to QtCreator 4.4...
tanks...

Found the error myself.
In the include dir there still was the file vtkGUISupportQtModule.h from the vtk-build included which defines

VTKGUISUPPORTQT_EXPORT __declspec(dllexport)

now its working

@VRonin said in Installare Qt in Windows ed utilizzo CMake:

Il messaggio che ricevi e' semplicemente dovuto al fatto che il tuo eseguibile non ha idea di dove le librerie di Qt siano.
Ti basta aggiungere il percorso alle librerie (ad esempio: C:\Qt\5.9\msvc2013\bin) alla variabile PATH. non conosco CLion ma molto probabilmente ci sara' un opzione per aggiungere quella cartella al "debug environment". in alternativa settala globalmente nel sistema operativo. apri cmd.exe come amministratore e digita SETX PATH "C:\Qt\5.9\msvc2013\bin;%PATH%" ovviamente cambiando il percorso per rispecchiare il tuo

Giusto, grazie mille!

CMake insists on creating the build directory, and it is annoying that you have to delete build directories all over the place when all you want to do is take a quick look at some sources. So creator "builds" in a temporary directory to extract information from CMake -- till you actually trigger an explicit build from creator. At that point the actual build directory is created and all the files go there.

You need to tell cmake to run your command in the source directory if those commands depend on being run from there: CMake usually does not build in the directory your sources are and will default to running stuff in the build directory.

@xiaocao Hi and welcome to devnet,

Then you should start by answering the questions I asked.

@Technologist If your kit is now fine (no errors/warnings), then it should work. Just try.

It went in but after the release of 5.8.0. So if you need it, either check the 5.9 alpha or build from Git.

Do you have a commericial license? The DataVisualization module was only added to the open source license (GPL) in Qt 5.7. Also, how did you install Qt? Using the online installer/maintenance tool, the examples are in sub-directories by version (e.g., C:/Qt/Examples/Qt-5.6), but yours doesn't not seem to use the versioned sub-directories structure.

Thanks !

Yes, i have some stuff that doesnt quite need to be there, but it doesnt hurt. I removed all possible linkings and made them "hardcoded". If i add blackflycam.cpp to the sources, therefore it is compiled, i get those errors. If i dont, all runs smooth. The thing is, the code that i replaced with that file, has the exact same includes and non of them are qt-related, so i dont know what the hell is going on here !

Is '-config Release' a valid command line option? I use -DCMAKE_BUILD_TYPE=Release

https://cmake.org/cmake/help/v3.0/variable/CMAKE_BUILD_TYPE.html

@ynirkin said:

It does work on debug configuration.
I did set the QT_QPA_PLATFORM_PLUGIN_PATH environment variable to "Qt\5.7\msvc2015_64\plugins\platforms" directory and I also tried to create a platforms directory in my exe directory and copy the qwindows.dll there.

You shouldn't set it to the "platforms" folder, but to the (parent) "plugins" folder instead.

@SGaist
Thank you very much! The wrong installer was the problem.

I solved this problem.

I just added this lines in my CMakeLists.txt

qt5_add_resources(QT_RESOURCES_CPP resources/qml.qrc) add_executable(my_app src/my_app.cpp src/my_app.h ${QT_RESOURCES_CPP}) target_link_libraries(my_app lib1 lib2 ...)

The problem was that I was adding my reference to QT_RESOURCES_CPP in the target_link_libraries(...) instead of add_executable(...). For some reason this didn't work properly.

Thank you,
Jonatan

Ok, then how did you install Qt ?