Diagnostics with tracing

[adzialocha]

No description provided.

[swick]

LGTM

[adzialocha]

This is not working yet as I cant get the env vars into the build process. Setting them in the builder config doesn't have any effect.

Im suspecting meson to not forward these settings but Im also a bit overasked ..

[swick]

will take a look later

[swick]

So, adding env to the build context really only adds them during the build. We can set the env for execution in finish-args:

diff --git ./org.p2panda.aardvark.json ../org.p2panda.aardvark.json
index bcbbd31..8d03175 100644
--- ./org.p2panda.aardvark.json
+++ ../org.p2panda.aardvark.json
@@ -12,17 +12,15 @@
         "--share=ipc",
         "--socket=fallback-x11",
         "--device=dri",
-        "--socket=wayland"
+        "--socket=wayland",
+        "--env=RUST_BACKTRACE=1",
+        "--env=RUST_LOG=debug"
     ],
     "build-options" : {
         "append-path" : "/usr/lib/sdk/rust-stable/bin",
         "build-args" : [
             "--share=network"
-        ],
-        "env" : {
-            "RUST_BACKTRACE" : "1",
-            "RUST_LOG" : "debug"
-        }
+        ]
     },
     "cleanup" : [
         "/include",
~

That works, but also means the app would ship to users like that. Ideally one could configure env in builder (Configure Project -> Applications). But unfortunately I can only choose the Run Command (Flatpak Application) but not set any environment.

Another way is to use a Command (Configure Project -> Commands) to spawn e.g. bash with "As Target Application" Locality and then just run "RUST_DEBUG=1 aardvark" there...

[swick]

rebased