Qt Creator and other tools

Thanks for sharing ! I do wonder if it shouldn’t be a bit more documented.

@J.Hilk Great! Thanks for sharing

@d_h_mcinnes then please mark this topic as SOLVED. thanks

Did you check your kit for any errors ?

@feldifux : I know its been pretty late xD but did you find any solution as I am facing currently the same problem? I tried everything possible but somehow just have an empty qmltypes generated by the qmlplugindump.

@fra_mecc Keep in mind that it is very easy to find the user name and password in your executable. So, if an user with a bit of knowledge gets your app he/she will extract the user name and password from the executable file.

@aha_1980 Thanks for the suggestion, I haven't tried the prebuilt yet, but I've been able to resolve this issue by compiling the source of LLVM and Clang 6.0 from http://releases.llvm.org/download.html I don't know why the two sources would differ so much, it might be worth investigating.

Only 5 months later, I've installed valgrind 3.13 and it's working :), though I had to patch it with https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=870419;filename=0001-Fix-parsing-of-xml-socket-argument.patch;msg=5 to make it work

Then take a look here in the Qt Creator manual.

@easythrees Shouldn't it be qmake.exe -spec win32-msvc -tp vc ? So, a dash before spec.

Unfortunately the above solution didn't work for me, $${TARGET_EXT} appears empty. BTW, the entire concept of building full path to the output file "by hand" appears to be limited. For instance, with TARGET=MyModule and TEMPLATE=lib, the output file is MyModule.dll on Windows but libMyModule.so.1.0.0 on Linux, so simple concatenation just doesn't work. It has to be a better way to pickup complete full path to the target file. QMAKE_RESOLVED_TARGET from mkspecs/features/resolve_target.prf seems to be a good candidate, but I'm failing to extract its value: it appears empty when I try to use it in QMAKE_POST_LINK. Qt community, please advise. Inability to specify arguments for post link step becomes a (very unexpected) shortcoming of qmake system and blocks our entire project.

@123456789 Yes, you need to read the docs about storage for QML and then decided if that is what you need. Then adapt the code you have to use the LocalStorage QML classes. There is none effort, just run solution for this. The sample you are using in archived which means its not up to date. So depending what you task is, i think LocalStorage is right for you.

@Chris-Kawa Understood. Thank you.

@istvan I just passed by the answer here: https://stackoverflow.com/a/46794723/7388116 In the newer version of Qt, this needs to be done to avoid a package not found error: QT_CONFIG -= no-pkg-config CONFIG += link_pkgconfig PKGCONFIG += protobuf #or whatever package here Also had to do this for Mac: mac { PKG_CONFIG = /usr/local/bin/pkg-config }

okay thanks!

@wrosecrans glad you got it working. so please mark this topic as SOLVED.