Application on MacOS not producing a .app gile so I can create a shippable executable
-
Ah, sorry,
written from scratch- I misunderstood that.Might be weird and it's been ages since I tried, but: what about two-step approach? You can ask qmake to prepare build files for the Xcode with
qmake -spec macx-xcode project.proorqmake ~/src/myapp -spec macx-xcode- the open the result in Xcode and try to build there?I am running out of ideas...
-
I finally sussed this. It was a number of things. In case it helps anyone on the future:
I found an article that suggested doing this on the command line in the source code folder:
make clean
qmake -config release
makeI still didn't have a .app in Finder but I did have one in the console so I am guessing ******** Finder is one of the biggest issues here. Probably does that really annoying thing Windows Explorer does by hiding extensions. Have never understood why a file explorer would do that. I could at this point run the macdeploy tool from the command line and produce an exxecutable.
At this point the STATIC build was a problem. Taking that out, meant it would run as a stand alone app.
This is all on 5.6.3 so the Qt version was also nothing to do with it.
-
Application bundle on macOS are indeed a special case. They are basically a folder with an extension following a special structure.
Here you have the complete explanation in the Apple documentation.
The Qt macOS deployment guide also talks about it.
