Open dhruvdabhi101 opened 2 months ago
First of all, I think this is a bug from Rust Port in metacall/core
, it is searching for metacalld, which is not correct because we have forced metacall to be always named libmetacall.so even if it is in debug or release mode. @josead told me about this bug before.
Another thing is, how have you installed metacall? Can you show all the commands..? Without full logs I cannot help you.
In another hand, if you want to install metacall, we are preparing the install script for MacOS, but meanwhile you have the pkg here: https://github.com/metacall/distributable-macos/releases/tag/v0.0.3
Here is how to install it, for example if you have ARM64 (M series):
sudo installer -pkg metacall-tarball-macos-arm64.pkg -target /
@dhruvdabhi101 I have updated the build.rs from Rust Port, let's see if it works properly now. It will publish a new version as soon it finishes the CI: https://github.com/metacall/core/commit/fc1d577cd5ad281a40656c3c8303a16287bcf877
@dhruvdabhi101 any news on this or I can close the issue? Now you can install by using the installer script: https://github.com/metacall/install?tab=readme-ov-file#install-linux-or-macos
It works for MacOS now.
I ran
./build.sh
and then it took large amount of time to install and at the end, it showed something like It doesn't have permission to read some file.When i check if i have metacall installed, then it was showing path as in Screenshot. And i tried to install
metassr
, it showed that,metacall
is no present. Is this the error ofmetacall
ordistributed-macos
. If yes, how can i fix it ?Device: Apple Mac M1 OS: MacOS Sonoma