Closed Arzte closed 1 year ago
Yeah, the latest release doesn't include Intel binaries for macOS, since I got an M1 Mac since the last release and haven't had time to figure out what was causing issues cross-compiling the native dependency (see #209). I'll probably automate the builds via GitHub actions or something instead of trying to cross-compile locally (again when I find the time).
The issue you're seeing with your local build is because the build script is hard-coded to use node 16 for the pre-compiled binary when packaging. The native dependency is built using your node version during npm install
and there's a mismatch between the ABI versions.
You can either modify the pkg arguments here to match your local node version (then do a clean install or rebuild) or just run the app build npm script (build:app
) without packaging which will output loose JS files and create a launcher shell script using your node version instead of the pre-compiled binary.
If you use the unpackaged version, keep in mind that the generated native manifest (which you can register via the install-manifest
npm script or moving manually to ~/Library/Application Support/Mozilla/NativeMessagingHosts/
) will point to the launcher script in dist/app/
which itself also sets the NODE_PATH
to app/node_modules/
, so you'll need to keep those paths in sync if you move anything around.
OS version: Monterey 12.4 Browser version: 101.01 Extension version: 0.2.0 Bridge version: 0.2.0
Description The bridge doesn't start up after installation, nor does run through the command line.
Steps to reproduce
Expected behaviour Bridge starts up after installation, or at least starts following running the executable in a terminal.
Logs
Additional Efforts Towards Finding a Working Solution I additionally attempted to build this myself since I just assumed it might have been compiled for M1 chips or something, however after installation, it failed for its own reasons, the following is the logs of the building and attempt at running the bridge. (It seems my node version is to new)
Console Logs (Spoiled for length)
``` ❯ git clone https://github.com/hensm/fx_cast.git Cloning into 'fx_cast'... remote: Enumerating objects: 7511, done. remote: Counting objects: 100% (2096/2096), done. remote: Compressing objects: 100% (757/757), done. remote: Total 7511 (delta 1385), reused 1964 (delta 1282), pack-reused 5415 Receiving objects: 100% (7511/7511), 8.49 MiB | 9.64 MiB/s, done. Resolving deltas: 100% (4877/4877), done. ❯ cd fx_cast ❯ git checkout v0.2.0 Note: switching to 'v0.2.0'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example: git switch -c