I'm on Big Sur and I have wxwidgets 3.2.0 and the latest kerl from Homebrew. When I try to build the required Erlang version, I run into this issue:

➜  ~ kerl build git https://github.com/diodechain/otp.git diode/beta 24.beta
Checking out Erlang/OTP git repository from https://github.com/diodechain/otp.git...
Building Erlang/OTP 24.beta from git, please wait...
DOCUMENTATION INFORMATION (See: /Users/nicd/.kerl/builds/24.beta/otp_build_git.log)
 * documentation  :
 *                  fop is missing.
 *                  Using fakefop to generate placeholder PDF files.

Build failed.
  const wxBitmap * Result = &This->GetBitmap();
                            ^~~~~~~~~~~~~~~~~~
2 warnings and 1 error generated.
gmake[3]: *** [Makefile:163: x86_64-apple-darwin20.6.0/wxe_wrapper_5.o] Error 1
gmake[3]: Leaving directory '/Users/nicd/.kerl/builds/24.beta/otp_src_git/lib/wx/c_src'
gmake[2]: *** [/Users/nicd/.kerl/builds/24.beta/otp_src_git/make/otp_subdir.mk:29: opt] Error 2
gmake[2]: Leaving directory '/Users/nicd/.kerl/builds/24.beta/otp_src_git/lib/wx'
gmake[1]: *** [/Users/nicd/.kerl/builds/24.beta/otp_src_git/make/otp_subdir.mk:29: opt] Error 2
gmake[1]: Leaving directory '/Users/nicd/.kerl/builds/24.beta/otp_src_git/lib'
gmake: *** [Makefile:498: libs] Error 2

Please see /Users/nicd/.kerl/builds/24.beta/otp_build_git.log for full details.
➜  ~ brew info wxwidgets
==> wxwidgets: stable 3.2.0 (bottled), HEAD

Looks like I'm running into this issue that's present on the iOS demo app too: https://github.com/elixir-desktop/ios-example-app/issues/3 that depends on https://github.com/erlang/otp/issues/5893.

What would actually be required to be able to use OTP 24 or 25 from asdf with this project? Would it be a lot of work? I don't have a lot of knowledge on this, or time, but I could take a look at least.

You mentioned in the README that the required changes have been added to master. I can't get an Android build working on Windows, would changing the otp source to otp24 be possible?

Hi! I try it. It is a magic. This is amazing project!

I think that run_mix has a wrong path. Would you please review this pull request?

I paste my smartphone screenshot.

Thanks!

My app immediately crashes on startup with

20:39:12.827 [error] ERROR: Could not find 'wxe_driver.so' in: /data/user/0/io.elixirdesktop.example/files/app/lib/wx-2.2/priv
20:39:12.834 [notice] Application desktop exited: Desktop.start(:normal, []) returned an error: shutdown: failed to start child: Desktop.Env
        ** (EXIT) an exception was raised:
            ** (ErlangError) Erlang error: {:load_driver, 'No driver found'}
                (wx 2.2) wxe_server.erl:65: :wxe_server.start/1
                (wx 2.2) wx.erl:115: :wx.new/1
                (desktop 1.4.1) lib/desktop/env.ex:28: Desktop.Env.init/1
                (stdlib 4.0.1) gen_server.erl:848: :gen_server.init_it/2
                (stdlib 4.0.1) gen_server.erl:811: :gen_server.init_it/6
                (stdlib 4.0.1) proc_lib.erl:240: :proc_lib.init_p_do_apply/3

Everything builds correctly though.

When I start my app, it crashes immediately with

Starting beam...
"/data/app/~~FKhNe6zQepp0iAw8dkkm4w==/io.elixirdesktop.example-OyaoOu7v7CwAl0mYQ0MkFQ==/lib/arm64/liberlang.so": ignoring DT_PREINIT_ARRAY in shared library!
{"init terminating in do_boot",{#{'__exception__'=>true,'__struct__'=>'Elixir.ArgumentError',message=><<"could not fetch environment variable \"RELEASE_SYS_CONFIG\" because it is not set">>},[{'Elixir.System','fetch_env!',1,[{file,"lib/system.ex"},{line,698}]},{'Elixir.Config.Provider','resolve_config_path!',1,[{file,"lib/config/provider.ex"},{line,185}]},{'Elixir.Config.Provider',boot,1,[{file, "lib/config/provider.ex"},{line,222}]},{init,eval_script,2,[]},{init,do_boot,3,[]}]}}

This is because in https://github.com/elixir-desktop/android-example-app/blob/d332169bcc968855848313f4bfda07d5e4d15027/app/src/main/cpp/native-lib.cpp#L99 the release is started in an unorthodox way, without running the release script. This means necessary env vars are not set.

I got it fixed with this kludge in that same file:

    setenv("RELEASE_SYS_CONFIG", config_path.c_str(), 1);
    setenv("RELEASE_ROOT", root_dir.c_str(), 1);

But I'm guessing for full compatibility either the startup should be changed to run the normal startup script (i.e. rel/<app>/bin/<app> start) or every env var from it should be emulated in a similar way as it does. I'm assuming the reason for starting the current way is to deal with Android specific stuff? I couldn't get it to start by calling the release script directly, but I'm really out of my depth in Android stuff.