So the answer to my question was you just need to launch apps from a <app>.desktop file put in "/usr/share/applications" path.
After finishing some Wayland stuff I wanted to get this Mir working for legacy targets like 16.04 Ubuntu Touch Mir targets.
Best posts made by zezba9000
-
RE: Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.
-
RE: Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.
@alan_g This is for legacy targets such as the "BQ Aquaris M10". It would be like saying targeting MacOS 9 or SNES is a bad idea (which its not given future goals).
Those targets can't change but I'm still interested in them as hobby/retro targets.I can't find documentation for Mir anymore. IDK if it was removed or not so I have no other group to ask who might know/remember what this issue might be. Anyway I'll look into this .desktop file.
-
RE: Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.
@arubislander said in Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.:
@zezba9000 Great write-up. Eager to try this.
Did you consider setting up the build environment in a Libertine container?
I'm not familiar with "Libertine". Does this make it easier to dev on X11? You have more info on this?
FYI now have Mir working in my Orbital-Framework and its implimented much better there.
Here is a link to that: https://github.com/reignstudios/Orbital-Framework/blob/master/Platforms/Lin/Shared/Orbital.Demo.Mir/Program.csMore code for Mir here: https://github.com/reignstudios/Orbital-Framework/tree/master/Platforms/Lin/Shared/Orbital.Host.Mir
Later I'll add GLES support but I need to get other graphic API stuff done in general in Orbital before I do that.
Anyway this makes Window creation very easy across platforms and now legacy Mir is supported.
Latest posts made by zezba9000
-
RE: Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.
@arubislander said in Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.:
@zezba9000 Great write-up. Eager to try this.
Did you consider setting up the build environment in a Libertine container?
I'm not familiar with "Libertine". Does this make it easier to dev on X11? You have more info on this?
FYI now have Mir working in my Orbital-Framework and its implimented much better there.
Here is a link to that: https://github.com/reignstudios/Orbital-Framework/blob/master/Platforms/Lin/Shared/Orbital.Demo.Mir/Program.csMore code for Mir here: https://github.com/reignstudios/Orbital-Framework/tree/master/Platforms/Lin/Shared/Orbital.Host.Mir
Later I'll add GLES support but I need to get other graphic API stuff done in general in Orbital before I do that.
Anyway this makes Window creation very easy across platforms and now legacy Mir is supported. -
RE: Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.
FYI here is a backup of legacy Mir stuff. Also working with C# via Mono or .NET 8 runtime.
I'll use what I have here to port into an actual C# framework. (Orbital-Framework)
https://github.com/zezba9000/MirClientWindow -
RE: Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.
So the answer to my question was you just need to launch apps from a <app>.desktop file put in "/usr/share/applications" path.
After finishing some Wayland stuff I wanted to get this Mir working for legacy targets like 16.04 Ubuntu Touch Mir targets.
-
RE: Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.
@alan_g This is for legacy targets such as the "BQ Aquaris M10". It would be like saying targeting MacOS 9 or SNES is a bad idea (which its not given future goals).
Those targets can't change but I'm still interested in them as hobby/retro targets.I can't find documentation for Mir anymore. IDK if it was removed or not so I have no other group to ask who might know/remember what this issue might be. Anyway I'll look into this .desktop file.
-
RE: Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.
@arubislander Ubuntu 17.04 has Unity8 session built in and directly supports Mir.
The mir-demos are the official Mir demo source code. The UBPorts 16.04 and Ubuntu 17.04 both are running Mir and both report the identical error.The reason I'm doing this is I want to target Mir in a framework I'm developing for legacy systems and platforms.
I'm just missing this final part in my understanding for what Mir apps need to be launched.This is the test/demo code I've been playing with: https://github.com/zezba9000/MirClientWindow/blob/master/TestMirC/main.c
-
Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.
So for homebrew testing I've compiled the mir-demo "fingerpain.c" in Virtualbox that runs in miral on Ubuntu 17.04.
I've compiled the same demo on my Aquaris M10 armhf device.In both Ubuntu "16.04 UBPorts Aquaris M10" and "17.04 Unity8" I've tried running the app via terminal that works in "miral" using this command.
export MIR_SOCKET=/var/run/mir_socket ./a.out
However I keep getting the error "Segmentation fault" actually running the demo on Mir/Unity8.
What is required to actually run a Mir app? Do I need to package it first before it will run?
I can't seem to find what I need to get it launching correctly.