Trying to make openxr work on Pico4 - static fails on silicon M1 osx.

[MarcWeber]

I tried getting OpenXR to work on Pico4.
the hello_xr from Khronos works.

However with Rust I get stuck at create_instance.
The pointer has an address and is not null but calling it doesn't return within create_instance.

The non static versions failed so trying static leading to cmake trying to install to /openxr
which cannot be done on OSX without heavy patching of security policies maybe nobody wants to do.

I also updated the OpenXR submodule (git submodule update --remote --rebase)
which at least allows to use current cmake 4.0.1 rather
than finding latest 3.26 which worked with the referenced submodule version.

But I get the same issue. So I guess either the way how cmake is run or the
cmake files should be patched cause updating failed ?

The working hello_xr from Khronos ships its own openxr_loader.so.

adb shell
  1|PICOA8110:/ $ find / -name '*openxr*' 2> /dev/null
  /vendor/etc/openxr
  /system/lib64/libopenxr_api.so
  /system/lib64/libopenxr_forwardloader.so
  /system/lib/libopenxr_api.so
  /system/lib/libopenxr_forwardloader.so

So looks like the one I tried shipping was found works with the C++ sample but
eventually not with Rust because I cannot find similar library on the Pico4
using find.

 [ 90%] Building CXX object src/loader/CMakeFiles/openxr_loader.dir/__/external/android-jni-wrappers/wrap/android.net.cpp.o
  [ 95%] Building CXX object src/loader/CMakeFiles/openxr_loader.dir/__/external/jnipp/jnipp.cpp.o
  [100%] Linking CXX static library libopenxr_loader.a
  [100%] Built target openxr_loader
  Install the project...
  -- Install configuration: "Release"

  --- stderr
  CMake Error at include/openxr/cmake_install.cmake:54 (file):
    file cannot create directory: /openxr.  Maybe need administrative
    privileges.
  Call Stack (most recent call first):
    include/cmake_install.cmake:47 (include)
    cmake_install.cmake:47 (include)


  make: *** [install] Error 1

  thread 'main' panicked at /Users/marcweber/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/cmake-0.1.54/src/lib.rs:1119:5:

  command did not execute successfully, got: exit status: 2

  build script failed, must exit now
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
note: If the build failed due to a missing target, you can run this command:
note: 
note:     rustup target install aarch64-linux-android

[Ralith]

However with Rust I get stuck at create_instance.
The pointer has an address and is not null but calling it doesn't return within create_instance.

Do you mean the create_instance call never returns? What's the backtrace?

cmake trying to install to /openxr

CMake shouldn't be trying to touch anything outside of target/. I don't have a mac, so I can't investigate this behavior for you, but feel free to send a PR if you find a fix. If the same problem occurs when trying to compile OpenXR yourself by hand from the upstream repo, then you should open an issue there instead.

The working hello_xr from Khronos ships its own openxr_loader.so.

OpenXR applications should always ship with a loader. That's what static linking does. If you're having trouble building your own, you could try reusing the one hello_xr ships.

[MarcWeber]

Search for XXX to find the android log (which should contain the backtrace if there was one !)
to find the create_instance calls. After reviewing it again: I can get the extensions list thus the loading of the shared library must have worked. I think I used the .so file from hello_xr (khronos SDK). But honestly I haven't checked whether the versions are the same BUT the .so file from the hello_xr worked in the rust android template.
Some guides told me to put the openxr_loader.so into a directory of the android app. So that's what I did.
So the idea was to use the static one to see whether it just works - but hit other problems that way.

log-failed2.txt

log-ok2.txt

Let's assume I am the problem, do you have an apk I can install to check whether your version just works ? I went through all the CPP / Rust code today again and didn't find any meaningful differences. Can there be something like a version mismatch between the rust .so and the loader ? I tried using latest revisions from this repo and that. So I hoped it would just be fine. I could try printing the sizes of the structs passed to XR* functions. If there is a big difference (new/removed fields) sizes might be different.

[Ralith]

(which should contain the backtrace if there was one !)

Please use a debugger to capture a backtrace to show where your process is hung. It's not something that will appear on its own.

That's if indeed your process is hung in an OpenXR call, which you haven't confirmed. Perhaps OpenXR is working fine, and your application logic isn't doing what you expect?

do you have an apk I can install to check whether your version just works

No, I have no personal experience with android development. This crate supports android only insofar as that people who need that contribute any necessary changes. I do know some folks have targeted Quest headsets successfully in the past, and you might be able to get the openxrs example working.

I could try printing the sizes of the structs passed to XR* functions.

That will not help.

[MarcWeber]

So the app seems to run. It looks like the window is there but no window (small arrow I can move) which hides/shows when going back to home. I tried catching the result. The prints don't appear. So no idea what is happening.
I traced by println it reaches the line where it calls the pointer but doesn't return. No panic nothing. The only thing I noticed between both logs that the thread id seems to change in the failed case.

        println!("app_name: {:?}", app_name);
        let xr_instance = match xr_entry.create_instance(
            // &Default::default(),
            &xr::ApplicationInfo {
                application_name: app_name,
                // application_version: app_version,
                application_version: Default::default(),
                engine_name: Default::default(),
                // engine_version: Default::default(),  // 0 ? 1_0 or 1_1
                engine_version: 0,  // 0 ? 1_0 or 1_1
                // api_version: xr::Version::new(0,0,0), // xr::Version::new(1, 0, 1),
                // api_version: xr::Version::new(1, 0, 1),
                api_version: xr::Version::new(1, 0, 0),
                // api_version:  Version::from_raw(0x0000002F as u64),
            },
            &enabled_extensions,
            &[],
        ){
          Err(e) => {
            println!("create_instance failed\n");
            println!("XXX ERR: {:?}", e);
            panic!("errro");
          },
          Ok(x) => {
            println!("create_instance succeeded :-) OK\n");
            x
          }
        };

I found many notes and hints that Quest is supported and works. I have a Pico4 :-) So I have to learn how to attach the debugger and step into whatever will be happening next. Makes sense.