Installation and Deployment

Thanks a lot! As expected, your changes didn't work here either but they gave me the clue I needed! I'm obtaining the path to the tool before that fragment, and all I had to do was enclose the code in a !build_pass { } block. !build_pass { TOOLPATH=$$shell_path($$TOOLPATH/$$TOOLEXE) message("Path to tool: " $$TOOLPATH) # Invoke the tool for a version check. TOOLVER=$$system($$TOOLPATH --ver) message(Tool version is $$TOOLVER".") TOOLMINVER=1.0.52 !versionAtLeast(TOOLVER, $${TOOLMINVER}) { message("Unsupported tool version " $${TOOLVER}".") error("We require tool version "$$TOOLMINVER" or greater") } } This means at some point during the qmake process the path is computed incorrectly. The !build_pass block solved it.

@smhrambo deleting the *.pro.user file often helps when you do such moves...

I don't know if this is going to be suitable for you (or for others). My suggestion would be to only keep one version of Qt and always remove the ones you currently don't need or don't want to build with. Makes the "Projects" selection much easier and prevents this kind of accident.

Looks like older compiler solved this topic.

@SGaist Thanks

Hi, welcome to the forum. Seems you're just missing an include: #include <QIcon>.

@caiomarcos he got succeed , but i can't get what he did. FYR https://forum.qt.io/topic/94378/qt-static-with-mysql-issue

@dblanch Hi and welcome to forum, Please give more details about what you are trying to do, your qt version yr compiler and your os so people can help you.

A possible Solution: after readings tons of threads I found one explaining how to compile the actual OpenCV 3.8 a single lib (opencv_world.dylib). (Sorry I lost the link from which I got the idea.) Than I included this into my pro file. After this I did clean, than I had to repast the whole code into QTCreator. After this - and only then - the code got recognized correctly and the calcHist function was found. Thx to everybody for helping. My actual *.pro file: #------------------------------------------------- Project created by QtCreator 2016-06-07T18:10:12 #------------------------------------------------- QT += core gui greaterThan(QT_MAJOR_VERSION, 4): QT += widgets CONFIG += sdk_no_version_check CONFIG -= app #QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.14 TARGET = CameraBox TEMPLATE = app DEFINES += QT_DEPRECATED_WARNINGS CONFIG += c++11 SOURCES += main.cpp mainwindow.cpp camviewer.cpp mywidget.cpp HEADERS += mainwindow.h camviewer.h mywidget.h FORMS += mainwindow.ui mywidget.ui INCLUDEPATH += $$PWD/. DEPENDPATH += $$PWD/. INCLUDEPATH += /usr/local/include LIBS += -L/usr/local/lib -lopencv_world debug: DESTDIR = $$PWD/debug/mac release: DESTDIR = $$PWD/release/mac OBJECTS_DIR = $$DESTDIR/tmp MOC_DIR = $$DESTDIR/tmp RCC_DIR = $$DESTDIR/tmp UI_DIR = $$DESTDIR/tmp

Hi @MrRobot, Glad you figured it out. So please mark this topic as SOLVED now. Thanks! PS: If you want to move a topic later, just ask a moderator to do so (if you can't do yourself).

Hi, What version of Qt are you using ? What version of macOS are you running ? What QML feature are you using ? What does the crash report of macOS show you ?

Hi, You have to build your application on the oldest Linux distribution you have to support.

UPDATE*** (In case others have similar problems) 9 Months later I went on tackling this problem. Turns out it was the file wall. It was preventing QtCreator.exe and QMake.exe from calling the cmd.exe. That is why when I was running things manually it would appear like everything was working just fine, but as soon as I tried to use QtCreator it would not work. I was actually able to go into the windows event logs and see the blocking event from occurring. After getting those white listed everything seems to be working good now.

So, finally, I got a solution (even 2 solutions): brackets. installer.executeDetached( "cmd", ["/C", "mkdir", "C:\\ProgramData\\My Company\\MyApp"], "C:\\ProgramData" ); With this trick even the addOperation() function works fine: component.addOperation( "Execute", "cmd", ["/C", "mkdir", C:\\ProgramData\\My Company\\MyApp"] ); I think this is closed.

@DSpider great! please don't forget to mark your post as solved. Thanks.

Hi, What exactly did you do ? What did fail ? What are you trying to use an outdated version of Qt ?

@KalleQt yep seems to be unresolved. :( I wonder if the other solution does work. https://stackoverflow.com/questions/46455360/workaround-for-qt-installer-framework-not-overwriting-existing-installation/46614107#46614107

@hskoglund Yep that was it - thanks

@BKBK OK, that's fine. But next time if you install Qt you should do it like I suggested - for me it was always working out of the box. Happy coding!