@noone said in QtFuture not found: workaround ? #include <QFuture>

AFAIK, it's the script that was used to bootstrap the port from qmake to cmake so it should do a pretty good job.

If possible maybe somebody could clone the repository and try it his computer to open project and run CMake. Not necessary to build the project (it may take 9 hours) but before launching CMake set build dir path as short as possible (I have build folder C:\S\b and the source C:\S\Slicer) because Slicer has some problems with path length and CMake will throw an error if build folder path is too long. I'm very interested in working on this project in QtCreator and not in Visual Studio but that QtCreator's behavior doesn't leave me any chances.

@noone said in no "Initial CMake parameters" field in Qt creator: what should I do ? Update to 4.13 :-)

ok late reply. found an easy fix for this. go to Tools -> Options -> Environment -> MIME Types type .cu in the Filter tab. (just to search for the right type) click on text/vnd.nvidia.cuda.csrc and clear the*.cu in the patterns tab. now type c++ in the Filter tab. click on text/x-c++src and add*.cu;*.cuh in the patters tab. dont clear whats alredy here.

@surferbrain You need to look inside that vcvarsall.bat file and see what paths it is trying to find/execute which cannot be found. Isn't the problem in your VS set up rather than Creator?

Well, huh. I thought I tried that one with the bigger project before, but it does work with the test program here, so that must have been something else. Thank you for your assistance.

@kdabros Hi! Did you manage to make a qmake based project for a VST plugin that you would like to share? I was just searching the forum for an example of that and your post was the closest thing I could find! Thank you, Ilias

@wokerjrvm How is your question related to the original question in this thread? Please open your own thread and ask there.

@ted-dr HI I hope developers would remove this feature or make it optional at least. This would become problematic with standard structured folders across multiple IDEs. Feel free to open an enhancement ticket and post link here. People can then vote for it, if they like you - feel the good old way was the best and if enough votes then it might happen :)

Are running this on two different computers (or VMs)? It seems there are more variables involved than just 'different version of QtCreator'. Working: Qt 5.12.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.3.0) on "xcb" OS: Ubuntu 19.04 [linux version 5.0.0-38-generic] Environment: QT_ACCESSIBILITY="1" QT_AUTO_SCREEN_SCALE_FACTOR="0" Not Working (note, QT_ACCESSIBILITY is not set): Qt 5.12.4 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 9.2.1 20191008) on "xcb" OS: Ubuntu 19.10 [linux version 5.3.0-40-generic] Environment: QT_AUTO_SCREEN_SCALE_FACTOR="0" Do you have additional KDE packages (not sure what that the 'kdedev' folder is) installed on the one that's working? Does your application depend on them? Can you run it in debugging to see where exactly it is crashing?

I have similar issue. It seems that contents from ANDROID_PACKAGE_SOURCE_DIR/res are not copied, and I need them to copy for splash screen, etc. If I copy them myself with this workaround: set(ANDROID_BUID_DIR ${CMAKE_CURRENT_BINARY_DIR}/android-build) #... file(INSTALL android/ DESTINATION ${ANDROID_BUID_DIR} FILES_MATCHING PATTERN "*") res contents does appear after cmake run, but once androiddeployqt runs (after build step), all these files disappear (being deleted?)!

@dmitry1992 https://doc.qt.io/qt-5/internationalization.html

I have the same problem on MacOS but this seems not coming from CMake but from the last version of QT Creator 4.11.x I installed an instance of Qt Creator to 4.10.x and get back project structure as folders structure.

Hi, It might be of interest and would likely benefit from a plugin in Qt Creator. However the first step would be to have it build various Qt project types. Note that cmake won't be transitional. It's going to be the build system of Qt 6 and thus it's going to stay like this for the whole Qt 6 lifetime at least. Just take a look at the lifetime of qmake.

@sierdzio Thank you.

HI CMake integration into Creator is very basic and we also had many issues with it not parsing the project file the first time. However it got a bit better with never Creators.

Hi, What version of Qt are you using to build Qt Creator ? How did you install it ?

You can have files with different rights anywhere on your system. One thing you can do is nuke that build folder then use chown and chmod on the content of your download folder and ensure that everything belongs to the correct user and with read/write properties.

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

I ran into the same problem and this problem is very very annoying during daily work. I filed a bug report for that issue.

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 ?