feat: `lib_dir` and `resource_dir` environment variables support about maa-cli HOT 6 CLOSED

I guess falling back to system library makes sense.

Perhaps std::env::current_exe can be wrapped with something like realpath in case it was executed from a symbolic link 🤔
e.g.:

~/.local
├─bin
│ └─maa -> ../stow/maa_cli-0.0.0/bin/maa
└─stow
  └─maa_cli-0.0.0
    └─bin
      └─maa

resource should also be in .local/stow/maa_cli-0.1.2, not somewhere outside.

from maa-cli.

std::env::current_exe has platform-specific behavior, which make it worse to just find lib and resource in current_exe's parent directory, when users make a symbol link from maa.exe to their Desktop or Startup Menu or so.

from maa-cli.

std::env::current_exe has platform-specific behavior, which make it worse to just find lib and resource in current_exe's parent directory, when users make a symbol link from maa.exe to their Desktop or Startup Menu or so.

The main reason we are currently searching for the lib and resource directories in the parent directory of current_exe is to accommodate users who may have installed CLI in various locations, such as ~/.local/bin. While this approach isn't ideal, it was chosen for its flexibility and as a fallback option.

However, when it comes to package managers, locating the lib and resource directories becomes much simpler. One potential solution is to introduce a compile time environment variable of lib and resource path for the package manager. This could potentially present challenges for prebuilt packages, such as Homebrew on Linux, where users have the flexibility to install packages in non-default locations, including within their home directories.

It's worth noting that the necessity for relocatability may vary among different package managers. If other package managers do not require it, this solution could be viable, since installing in non-default locations is discouraged by Homebrew.

Search MaaCore.so in LD_LIBRARY_PATH will be greater.

I believe it's a good idea and aligns with the default behaviour of dlopen. I'll delve into this further to explore its feasibility.

from maa-cli.

I just add support for search LD_LIBRARY_PATH.

I'm interested in hearing your opinions about the environment variables. @Cryolitia, what are your thoughts on this? And @horror-proton, I'd also like to hear your perspective.

from maa-cli.

With the resolution of the current_exe issue and the support for searching system libraries, I believe there is no need for additional environment variables. Consequently, I close this issue as completed. Feel free to reopen it if you think it was not resolved.

from maa-cli.

That's great!

with commit 32c0857 , there's also no need for resource_dir.

Thanks for your hard work.

from maa-cli.