We had a similar problem. There does not appear to be any purpose for a lot of the stuff that Qt Creator piles into the ".app" file, and it interferes with Apple Notarization.

We solved the problem by simply creating a command file that deletes the conflicting files:

# Clean out detritus that prevents notarization cd foo.app find . -name "*.h" -delete find . -name "*.prl" -delete find . -name "*.cstemp" -delete find . -name "Headers" -delete find ./ -name "*_debug" -delete

Have a look at the State Machine Framework documentation here.

Basically make one state with your defined transition, and create your other states accordingly with the parent state that has your single transition defined.

Good luck.

@KMKT Hi, and sorry for the late reply.

libarchive support is enabled in the official Qt IFW binaries, and for the upcoming 4.3 release it does the handling of all archive formats including 7zip. The reason it's behind a separate config feature is that libarchive requires linking against additional libraries in comparison to the LZMA SDK distributed with the Installer Framework, so we didn't want to force the changes to the users' build environments.

However, even after migrating the 7z format to libarchive, there have still been some findings about occasional memory allocation failures when extracting large archives. Moving the IFW binaries to 64-bit on Windows should hopefully finally fix these issues. The user story is tracked here QTIFW-2544, and is something targeted for Qt IFW 4.4.

@patrik08 : I am trying to mix normal QT application with Swift code in order to load the receipt of purchasing an app from app store as requested in this, since you have good experience with Swift and QT C++ code, i would appreciate if you provide an example for this case to the tracker. Thanks alot

https://bugreports.qt.io/browse/QTBUG-76665

Hi,

I may be wrong but AFAIK, Apple changed recently its policy about dynamic library in application bundle. Thus its likely related to that.

You should bring this question to the interest mailing list, you'll find there Qt's developers/maintainers. This forum is more user oriented.

@Peppy Right now it just won't work without installation, however you can install it separately from Qt (just point QMAKEPATH to proper location)

@patrikd
Thank your suggestion worked fine for my framework too.
Wish I could give you a cartload of reps for that :-).

Since the obvious answer to the question is a resounding 'no', I'll mark this question as 'solved', although I'll still have to think about a way to achieve what we want in the most convenient way.

@Pt_develop hi Can you share the example of what you did
How you created the desktop shortcut and copied it.

I found the answer. The problem is that the QtWebKit.framework bundle requires some of these other ones, even though I might not be using them. The only fix would be to acquire the QtWebKit.framework project, remove the QML and Quick dependencies, recompile, swap that framework bundle out of my project after macdeployqt, and then remove the QML and Quick framework bundles.

Long story short, that ain't happening. Not worth my time because it's super difficult.

You can find additional information in the qmake platform notes

Hi and welcome to devnet,

Unless you're using an old version of Qt, the mkspec for VS2015 is already in so you can build Qt with it.

As for jom, you can just call it in place of nmake. Use the full path to the exe and you should be good to go.

Hope it helps

Thanks for the help.

But the real reason was that, I was using wrong version of QT for my project. My project supports QT version upto 5.4 & I was using 5.5. After downgrading all works fine now.

Thank you, turned out it could be done like this:
QMAKE_POST_LINK += $SCRIPT_PATH $ARG1 $ARG2
No need for system()

Hi,

The only good answer is: benchmark.

In any case, Qt's State Machine Framework is not know to be slow so unless you're expecting speed of light it should run well enough.

これで行けました。

function Controller()
{

}

Controller.prototype.FinishedPageCallback = function()
{
buttons.CommitButton.hide();
}