kpackage: reasons not to use ecm_mark_nongui_executable?

[René J. V. Bertin]

Alex Merry wrote:


> I would expect that they should be nongui. We've realised that there are
> some cases where we want to be marked GUI on windows and not on OS X,
> but I doubt that's the case for KPackage.

Do you know if applications marked non-gui initialise the windowserver 
connection on startup, on OS X? Apps that don't will crash when they attempt to 
do anything GUI or event processing related, but apps that do cannot be run from 
a remote terminal if the same user is not logged into the desktop too.

Only side-ways related: is there an ECM macro to mark an application as an 
"agent" That's OS X jargon for an application that can put up a GUI (and thus 
will typically live in an app bundle though that's not a hard requirement) but 
that should not show up in the app switcher and the Dock. Usually these are 
daemons like kglobalaccel but they can also present just a "systray" icon and 
menu, like kwalletmanager .
When these applications live in an app bundle, they can usually be turned into 
an agent by setting the LSUIElement property to true in the Info.plist, which is 
something that could be under CMake's control.

R.