@IgKh Thank you for your precious help, things are a lot clearer now. Further tests have shown that most of the features I need still work without a call to exec(). I still can't quite understand what in my example started the event loop or if Qt just plugs in the existing NSApplication's event loop. @IgKh said in Building a DLL on macOS for a non Qt application: Had no effect on the main issue though Can you, just for sake of clarity, state the remaining issues? The main issue i refered to was me wanting to have a separate thread with a QApplication in it and the Qt::AA_PluginApplication attribute had no effect on this. The other issues I have are not within the scope of this topic though. Thank you very much !

Run it on the binary of your application.

@Guy-Radford This appears to be a bug as the CAN Frames are decoded correctly on a windows machine, I have raised a Bug report with QT: https://bugreports.qt.io/browse/QTBUG-113538

Hi, You can open a feature request to discuss that matter.

Hi, Are you using the same stack on macOS ?

If anyone interested, the reason behind that error is that you apparently cannot run unsigned apps on M-chips: https://github.com/orgs/Homebrew/discussions/3088. To fix this just self-sign the app bundle: sudo codesign --force --deep -s - toolbox.app

@Dariusz You should use macdeployqt for all things qt, possibly your custom solutions for your custom stuff (additional libs, etc).

Libraries that are shared between plugins and executable shall be shared and not static. Otherwise you will end up with multiple definition of the static meta object of your QObject based classes which is not good.

Hi and welcome to devnet, AFAIK yes. I am currently unsure about native M1 pre-built package being available but even with the x86_64 you should be able to get started.

@Nathan-Barel Yes it seems fixed in 5.12 and 5.15 [image: ManV1r.png] https://bugreports.qt.io/browse/QTBUG-87014

Great ! Since you have it working now please mark the thread as solved using the "Topic Tools" button or the three dotted menu beside the answer you deem correct so other forum users may know a solution has been found :-)

@DerReisende Thank you. I will try it.

Thank you @SGaist , filed a bug report.

Right, I forgot that part. The "workaround" is explained in the QKeySequence documentation linked from the QShortcut one.

Glad you found a solution ! Would you mind sharing the changes you made ? You might even consider including them in Qt directly ?

@kenchan - Again, thanks. I've successfully used -Wno-missing-braces on the analyzer and editor, so it 'works' for at least some versions of the compiler. As for 'warn_on'/'warn_off', I had no trouble verifying their existence/function once I found them in the .pro file, but I had no prior warning to look for such a thing. I've been looking for QMAKE_CXXFLAGS, not weird macros that are defined in some middle ground between the .conf files and the .pro files. I don't understand how the .conf files work, much less how to successfully invoke half of the options documented there and elsewhere. On the other hand, I think that I've solved my main issue with the discovery of the hidden 'warn_off' in my library's .pro file. I have compile warnings again. More than I'd like, true, and I don't seem to be able to turn off specific warnings, but fixing the autogenerated code should get rid of the majority of the offending bits, so I can at least have some confidence in my builds again.

It does look like a similar issue. I was able to find a workaround thanks to this bug report. Setting the target OSX version to 10.12 in CMake did the trick.

@SGaist, could You provide an example please - fixed mylibrary.pro? Thanks!