Qt Creator and other tools

@aha_1980 thanks , I'll check that out

The workaround is to disable the check for xcode versions in mkspecs files, to do this prepend false: before lessThan(QMAKE_XCODE_VERSION in those files : mkspecs/features/uikit/default_pre.prf:24 mkspecs/features/uikit/default_post.prf:42 mkspecs/features/uikit/bitcode.prf:1 For default_pre.prf, line 24 should then be: false:lessThan(QMAKE_XCODE_VERSION, "4.3"): \

@LeLev said in QML Compiler [this qt version does not contain Qt Quick Compiler]: So why i have : "this qt version does not contain Qt Quick Compiler" warning in Qt Creator Project tab Probably it was not on the radar of creator devs. You may want to check with JIRA

Hi @steve37, my gut feeling tells me the QBS build could be a release build with additional debug information (i.e. non-stripped). You'll have to dig a bit deeper within, and e.g. issue file on some of the generated libraries - that should give some insight. Regards

It turns out using qt.conf under the same directory as qmake solves the problem. It can be used to set the paths properly within the cross-compilation toolchain: Using qt.conf

Qt Creator 3.5 is quite old. Maybe try if your problem persists with a newer Qt Creator, like 4.7 from our prebuilt binaries at https://download.qt.io/official_releases/qtcreator/4.7/4.7.1/

Is it possible you have files with the same name in different folders? I have had once a case where one main.o had (partially) overwritten another main.o generated from two different source files.

I am pretty sure it comes from the debugger - which is from the MS Visual Studio toolkit! I think I do not need to recompile the entire thing with mingw only to find this confirmed: It would take me probably several days with all the related modules... Anyway, I could imagine to either have some "switch" to shut up the debugger (including a trick how to apply it from inside the QtCreator), or some option in the QtCreator itself that filters these messages out. Actually I did not only switch from an earlier version of QtCreator to now 4.7.1, but also from MSVC 2013 to 2015 at the same time, so the problem could come from the one or the other. (And you are right: chances are high that it is actually the MSVC 2015 debugger...)

Hello again! I've been testing for a bit more than an hour now and it still haven't crashed. Yay! I guess we can say it's fixed. Thank you for the hint.

Hi, Might be a silly question but are you sure that this function is not called several times with the same file ?

@jsulm thank you very much i have solved my problem but if you want i can send you if you like . i used (KOI8-R)

Hi "I think we need to drag and drop a Qt Bridge ZXP package to the Adobe ZXP installer, but I haven't found this package, please feel free to help." Im sorry but this makes no sense at all :) Can you provide more information ?

@jsulm I am not shure if it thread can help me, but my compiler say: "can not find this(Qt3DRender::Render::ResourceAccessor::OGLTextureRead) symbol" qt3dstudio/qt3druntime/src/runtime/aping/q3dsstudio3dengine.cpp:491:70: error: ‘OGLTextureRead’ is not a member of ‘Qt3DRender::Render::ResourceAccessor’ ra->accessResource(Qt3DRender::Render::ResourceAccessor::OGLTextureRead, layer.textureNodeId, (void**) &tex, nullptr); if I look here, i should find the Qt3DRender::Render::ResourceAccessor::OGLTextureRead symbol here?

@Jonathan-Levanon So please mark this topic as SOLVED. Thanks!

Thanks -- I had a bad feeling it would be easy... Best Regards, Tobias