Qt Creator and other tools

@6thC said in Problems with using Creator: I was just pointing out that within Creator you can edit ui.qml files when in text mode. Are we not talking about the same files? Definitely no! Refer to my first post in this thread: @koahnig said in Problems with using Creator: @pintovillamar I am not sure what the issue is, since I do not do qml.

So I finally did it. In both case (from repo & sources), I had qmake 3.1 but I think , somehow, qmake wasn't able to find qtwayland library (which was installed). By compiling qt5 myself, including qmake and all the submodules (I did it wildly), everything is connected. Maybe I could have done it by adjusting VARIABLES like QT_HOST_LIBS or QT_INSTALL_HEADERS to point where qtwayland was installed but I didn't found how at the moment. I solved my problem but can't tell what was the original issue with the repo package. Thanks anyway. So long.

Hi Just to be clear QtCreator is version 4.4.1.(newest) And it the IDE/editor Qt version is not tied to creator. you can use any Qt version with it. Like Qt4.8 (old gen) or Qt.5.9/10 (newest) If you have Qt4.8 based code, it might need some porting to run in Qt5.9 Some classes have changed. Also, QtScript is deprecated and superseded with QJSEngine but still fully functional in later Qt version. ( whole of 5.X as i understand it) There is a tool to debug QScript http://doc.qt.io/qt-5/qtscriptdebugger-manual.html And you can use http://doc.qt.io/qt-5/qscriptenginedebugger.html to embed into the app. I assume this is how you use js ? I mean via QScript ?

@Son-Nguyen said in QT Creator 5.9.3, 32 bits, QT quick application build fail?: the build fail in detail: project cannot see the source path at project and build fail: cannot run compiler g++. May be you forgot to setup the environment?

Hi <warning - we like newbies > I assume you mean you want to step inside QScriptEngine to see what it does. On windows, visual studio pdb files are provided but as far as i know, on other platforms you would have to compiled your own debug version of Qt to step into code. ( with configure -debug xxx) The Qt that is shipped is in release mode and hence it cant step into it. Alternatively , you can use https://code.woboq.org/qt5/ which is super good at browsing the code as all uses of a function is hyperlinked and it can show uses. Almost as good as "being there" [image: M17SKS.png]

Yes, that's totally an option! Still I'm curious to know if this can be done with QBS... I'm porting a couple of big projects to it and I'm trying to test every feature of this tool, which I think it's great! But, anyway thanks for the tip!

@jsulm GOT IT WORKING! removed installation, removed all configuration directories (.config, .local/share) for both user and root. Probable a rest from the previous qt4 installation that caused the problem

It does it inside some functions for the this but in any function for the value of a QSharedPointer. So I guess the problem with this isn't really a problem, but for the QSharedPointer, it wasn't like this before... I've always been able to open it and see the pointer (or NULL if it is not instanciated)

Thanks everyone! I solved this problem by rebuild python with "--enable-shared" Here are some references: https://danieleriksson.net/2017/02/08/how-to-install-latest-python-on-centos/ https://stackoverflow.com/questions/43333207/python-error-while-loading-shared-libraries-libpython3-4m-so-1-0-cannot-open

@CoBo said in Different *.user file extension for Windows and Linux?: First of all the fact that despite of several efforts I finally never really understood the way how git is working: It is somehow "different" than CVS and SVN (which are somehow "logical" for me), also it must be somehow "genial", but how? I hate it to jump on such a train without some basic understanding of what I am doing! Yeah, getting off-topic, so I'll stop here also. But one last hint: just start using git. I did it also - and learned on the way. first you only need to commit your changes. Later you will learn all the other stuff. Yeah, and a second one: do backups. Until you are fluent with git and push your changes to an other station, do at least file system based backups. I still combine both and it works very well for me.

@SGaist Yeah, that was an accident. I had two questions, with one of them needing to be in that section and I accidentally put this one there too. Thanks for your help! I'll follow your tips.

Thanks guys for the great tool it solved my problem

on macOs add this to .pro install armadillo: brew install armadillo brew list armadillo INCLUDEPATH += /usr/local/Cellar/armadillo/8.200.2/include/ LIBS += -L/usr/local/Cellar/armadillo/8.200.2/lib/ -larmadillo

This Debugger Console is most probably just for QML debugging as suggest the text: "Context: Global QML Context" in the screenshot in http://doc.qt.io/qtcreator/creator-quick-tour.html

This has very little to do with Qt... INCLUDEPATH += Right Click on the project file -> properties -> C/C++ -> General -> additional include directories LIBS += -L Right Click on the project file -> properties -> Linker -> General -> Additional library directories -l Right Click on the project file -> properties -> Linker -> Input -> Additional dependencies you have to do it separately for Debug and Release

Sorry for trouble it was my bad. I tried to use Qt 5.6.3 for Windows 64-bit with build tools for visual studio 2017 but now I downloaded Qt 5.9.2 for Windows (2.2 GB) (info) and it seems to work just fine.

I found a solution with QMAKESPEC message("SPEC " $$QMAKESPEC) message("SPEC " $$basename(QMAKESPEC)) The output is for instance: Project MESSAGE: QMAKESPEC C:/Qt/5.4/mingw491_32/mkspecs/win32-g++ Project MESSAGE: SPEC win32-g++ or on linux Project MESSAGE: QMAKESPEC /home/bloblo/Qt/5.9.1/gcc_64/mkspecs/linux-g++ Project MESSAGE: SPEC linux-g++

@quadbyte: There is QTCREATORBUG-19004 which looks like your problem. Please see there for more information about the problem and the possible solution (upgrading valgrind)

In Options->Build and Run->Kits, after selecting your kit at the top of the options window, the settings will be shown down below. One of those options is 'CMake generator'. Press the 'Change' button for that option and you will be able to select 'NMake Makefiles JOM' as your generator.