Anyone? T_T

After building the VTK using Qt5.13.2, I uninstalled the Qt version since I already have 5.12.6. While running a sample code to check the VTK plugin I m getting the following linker error: 09:49:20: Running steps for project pcl_visualizer... 09:49:20: Starting: "/usr/bin/cmake" --build . --target all [ 20%] Automatic MOC and UIC for target pcl_visualizer [ 20%] Built target pcl_visualizer_autogen [ 40%] Linking CXX executable pcl_visualizer /usr/bin/ld: /usr/local/lib/libvtkGUISupportQt-7.1.so.1: undefined reference to `qt_version_tag@Qt_5.13' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/pcl_visualizer.dir/build.make:254: pcl_visualizer] Error 1 make[1]: *** [CMakeFiles/Makefile2:77: CMakeFiles/pcl_visualizer.dir/all] Error 2 make: *** [Makefile:84: all] Error 2 09:49:21: The process "/usr/bin/cmake" exited with code 2. Error while building/deploying project pcl_visualizer (kit: Desktop Qt 5.12.6 GCC 64bit) When executing step "CMake Build" 09:49:21: Elapsed time: 00:01. I m using CMake system and I tried the solution given here but it is not working. Should I create a different thread for this?

Correction. I do not why. But my proposal no more works. But I found another way that seems to work. In fact the QDiffuseSpecularMaterial that we are supposed to use (other materials are deprecated), disable the depth buffer. So, this is a working code to force the enable (create a new effect does not work): Qt3DRender::QEffect *effect = material->effect(); if (effect) { for (Qt3DRender::QTechnique* currentTechnique : effect->techniques()) { for (Qt3DRender::QRenderPass * currentPass : currentTechnique->renderPasses()) { for (Qt3DRender::QRenderState * currentState : currentPass->renderStates()) { if (dynamic_cast<Qt3DRender::QNoDepthMask *>(currentState)) { currentPass->removeRenderState(currentState); Qt3DRender::QDepthTest* depthTest = new Qt3DRender::QDepthTest; depthTest ->setDepthFunction(Qt3DRender::QDepthTest::Less); currentPass->addRenderState(depthTest); break; } } } } } Warning: if you have fully transparent (alpha = 0) objects, the test fails. So the objects behind the invisible one are not displayed.

@Alain38-0 OK. Now I have found a way to always have a displayed text. For this, in the initial setText (when scene is not yet rendered) I'm putting all the characters that can appear in the strings that will be displayed. Then, I have something displayed. But it is often wrong. To be more explicit I'm doing this: void createScene() { ... myTextEntity->setText("?CLRT0123456789"); ... } void pageDisplayed() { ... myTextEntity->setText("???"); ... } void onButtonCLicked() { myTextEntity->setText("C23"); } setText("C23") displays another string of three characters (like "2R7"). But, at least strings have a coherency (all 'L' are replaced by '0', and so on).

@Strohhut no problem, I was close to the end of my suggestions... So great it's not working ! Setting up a working android toolchain can be cumbersome 🙈 Son't forget to use the topic tools to set the topic to solved :)

@porridgechef Hi and welcome to devnet forum This is a user driven forum where you might get help in case you need better understanding of functionality. Basically nobody in this forum is able to predict exactly what features may come. There is the bugreporting tool where also feature requests may be placed. https://bugreports.qt.io/secure/Dashboard.jspa Have a look there and check if the feature is already placed. Otherwise you may it and it may be implemented some time in the future.

@sneubert Thanks :)

Just wanted to say thanks! I ran into the same issue (building qtwebengine) on Ubuntu 18.04 host and this fixed it. I'm adding it to my personal list of prerequisites for my Boot2Qt Yocto builds....

Hi @ivec Is it normal that I needed to select the compiler manually? No. but please select the C compiler also. And how can I enable the use of a debugger to step through my program? You need to install the Debugging Tools for Windows, included in the Windows SDK. Due to licencing, this is not possible otherwise. Regards

@andyDT What do you see when you put the mouse cursor over that red exclamation mark? My guess is that qmake was build for ARM not x86.