If you mean just Kernel + Gui development then no need in two packages.
Combine them both.
And no problem in SailfishOS to communicate between processes. You can
use any favorite method. Everything works.
On 26.02.2014 14:50, Kaj-Michael Lang wrote:
On Tue, 2014-02-25 at 21:43 +0100, Randolph
On Tue, 2014-02-25 at 21:43 +0100, Randolph wrote:
> Not the same question for sailfish, is it here the same? does the RPM
> for kernel and RPM for gui will be able to communicate or is this
> prohibited too?
For native apps you can use any standard unix/linux IPC method available
to communicate.
dbus?
Zitat von Randolph :
Hi there
one question for sailfish. When a Qt app with gui and kernel are compiled
to android, then android has two apk installers, one for gui and one for
kernel. But both cannot communicate in android, as this OS does not allow
the communication of one app with the
Sailfish is GNU Linux, not Android.
Why you need two packages?
On 26.02.2014 02:43, Randolph wrote:
Hi there
one question for sailfish. When a Qt app with gui and kernel are
compiled to android, then android has two apk installers, one for gui
and one for kernel. But both cannot communicate i
Hi there
one question for sailfish. When a Qt app with gui and kernel are compiled
to android, then android has two apk installers, one for gui and one for
kernel. But both cannot communicate in android, as this OS does not allow
the communication of one app with the other.
Qt 5.4 might solve this
