"haxelib install ceramic" on macOs appears to only provide a arm64 electron binary

[hermanhermitage]

On an Intel based macbook pro, I ran "haxelib install ceramic", and tried to build an launch following instructions at https://ceramic-engine.com/guides/your-first-project/

$ ceramic init --name myproject
Project created at path: /Users/user/Projects/crosslanguage/haxe/ceramic/myproject
Updated clay hxml at: /Users/user/Projects/crosslanguage/haxe/ceramic/myproject/out/clay/web/project.hxml

$ cd myproject

$ ceramic clay run web --setup --assets
Will build with configuration Run for target web (Web).
Updated clay hxml at: /Users/user/Projects/crosslanguage/haxe/ceramic/myproject/out/clay/web/project.hxml
Update project assets
Update project icons
Run begin build hooks
Run haxe compiler
Copy from Web project template
Perform replaces in names
Perform replaces in contents
Start ceramic runner
Failed to start electron: exited with status 126

$ file $(find ~/ceramic/ -iname electron -type f)
/Users/user/ceramic//runner/node_modules/electron/dist/Electron.app/Contents/MacOS/Electron: Mach-O 64-bit executable arm64

$ file $(find ~/ceramic/ -iname haxe-bin -type f)
/Users/user/ceramic//git/haxe-binary/mac/haxe/haxe-bin: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64]
/Users/user/ceramic//git/haxe-binary/mac/haxe/haxe-bin (for architecture x86_64):	Mach-O 64-bit executable x86_64
/Users/user/ceramic//git/haxe-binary/mac/haxe/haxe-bin (for architecture arm64):	Mach-O 64-bit executable arm64

$ uname -a
Darwin Users-MacBook-Pro-3.local 20.6.0 Darwin Kernel Version 20.6.0: Thu Jul  6 22:12:47 PDT 2023; root:xnu-7195.141.49.702.12~1/RELEASE_X86_64 x86_64

Looks like the electron node module doesnt include a universal binary, or a x86_64 binary.

Apologies I'm out of my wheelhouse otherwise, I'd try and fix it.

[hermanhermitage]

I note also that some scripts are using readlink -f but I at least on my version of macOs that is not supported.

[jeremyfa]

Ah, shoot, didn't notice electron isn't an universal build! As a workaround, you could go to ceramic/runner/ directory and run npm ci (maybe remove the existing node_modules folder before that). That should install the correct binary for your machine. (you'll need nodejs to do that)

Will have to figure out how to make sure this is an universal build though.

What version of macos do you use?

Regarding the readlink -f usage I suppose you are talking about the haxe and haxelib scripts. Maybe you could try to replace the SCRIPT_DIR=... with this:

get_script_dir() {
    local source="${BASH_SOURCE[0]}"
    # Resolve $source until the file is no longer a symlink
    while [ -L "$source" ]; do
        local dir="$(cd -P "$(dirname "$source")" && pwd)"
        source="$(readlink "$source")"
        # If $source is a relative symlink, resolve it relative to the path where the symlink file was located
        [[ $source != /* ]] && source="$dir/$source"
    done
    cd -P "$(dirname "$source")" && pwd
}
SCRIPT_DIR=$(get_script_dir)

(didn't test it, but if that works for you, I may change the script accordingly in the next Ceramic udpate)

[hermanhermitage]

macOS Big Sur, 11.17.10 (very old, but its all that runs on this macbook pro 2013). Does more modern macos have a updated readlink? or maybe the test environment has coreutils/greadlink installed?

So confirmed switching to your get_script_dir() works.

[hermanhermitage]

@jeremyfa I now just tried your first suggestion and success! Thankyou so much. I installed latest node/npm. I cd ceramic/running; npm ci and it did its thing. Now when I ceramic clay run web --setup --assets it launches electron successfully and runs. Again, thankyou kindly. I'm super stoked. I've been lurking forever wanting to use haxe for some projects and now with ceramic it looks like it ticks all the boxes for my use case! Terrific.

[jeremyfa]

Nice! I'll see how I can solve the missing architecture in next Ceramic release, and update the scripts using readlink. I think readlink -f is working starting from macOS 12+, which would explain why it fails on your setup