Qt app on mac

[T_oni]

@SGaist
With application bundle you mean the compiled installer, if I understand correctly.
My MyAppInstaller.app structure is as follows:

• MyAppInstaller.app
  • Contents
    • Frameworks
    • Info.plist
    • MacOS
      • MyAppInstaller
    • PkgInfo
    • Resources
      • MyAppInstaller.icns
      • installer.dat
        Now that you asked the question I wonder where it should be located....

[SGaist]

What does the installer do exactly ?

[T_oni]

@SGaist
(I realised the structure was weirdly missformed, I edited it.)
The Installer is supposed to install MyApp in the "home directory" which works fine.
The App is later supposed to start automatically at boot, therefor when the installation-wizard it done, the App is supposed to start automatically.
(Basically the user shouldn't open the App themselves at all)
I hope that helped.

[SGaist]

How do you start the application at the end of the installation process ?

By the way, why the home directory ? That feels odd with regard to macOS standards.

[T_oni]

I use the home directory right now, just to have something to test with. I want to change it later, so the user can choose the directory themselves.

This is the code, to call the application after the installation process:

function Component()
{
    installer.installationFinished.connect(this, Component.prototype.installationFinishedPageIsShown);
    installer.finishButtonClicked.connect(this, Component.prototype.installationFinished);
}

Component.prototype.createOperations = function()
{
    component.createOperations();
}

Component.prototype.installationFinishedPageIsShown = function()
{
    try {
        if (installer.isInstaller() && installer.status == QInstaller.Success) {
            installer.addWizardPageItem( component, "page", QInstaller.InstallationFinished );
        }
    } catch(e) {
        console.log(e);
    }
}

Component.prototype.installationFinished = function()
{
    try {
        if (installer.isInstaller() && installer.status == QInstaller.Success) {
            	installer.executeDetached(installer.value("TargetDir") + "/myapp/./main.py");

         }
    } catch(e) {
        console.log(e);
    }
}

[SGaist]

@T_oni said in Qt app on mac:

/myapp/./main.py

That's a strange path.

Why not start the app bundle ?

[T_oni]

That is the app bundle (At least in my understanding).
That is the installed app and inside it (the main.py) is the main code.
Or is it not? I'm sorry, maybe I didn't understand it correctly?

[artwaw]

@T_oni You should not call anything inside the bundle. By default the bundle (.app) is the only executable you should call.
More info https://developer.apple.com/library/archive/documentation/CoreFoundation/Conceptual/CFBundles/BundleTypes/BundleTypes.html#//apple_ref/doc/uid/10000123i-CH101-SW13

How do you deploy bundle, how do you put deployment files in it? Does it pass the validation from Gatekeeper? Do you sign the code properly?

[T_oni]

@artwaw
Thank you for the link, I will read the information.

I used this command to make the executable app with Qt Installer Framework:

/Users/myname/Documents/qtinstallerframeworkmac/bin/binarycreator -c config/config.xml -p packages MyAppInstaller.app

With this command I than have the installer, that the user is supposed to double-click on to install MyApp. When MyApp is installed it is a folder-structure. And inside that is the main.py that I am executing after the installer is finished. However that only works when I execute the installer over open command.

I unfortunately don't know what you mean with "validation from Gatekeeper".
I'm going to look into it, though. Thank you.
Edit: I have looked into it, however until now I didn't run into Gatekeeper at all with my application. So I'm not sure, if this has anything to do with it. And if, why does my app run fine, when I execute the installer over the terminal?

[T_oni]

Edit: I solved it. Or better said, the problem is gone.
I made the application executable by using pyinstaller. I used to just give the command my path to the application. However, my application runs in a virtual environment.
Installing pyinstaller in said virtual environment and executing the command while still in the virtual env, the problem with the double-click was resolved.