build fails on MacOS: xcframework ghostty-vt failure
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- cmake, macos, zig
- Domain
- build-system
Research direction
Reproduce the failure with the reported Zig 0.15.2, CMake 4.3.1, and macOS setup by running make clean build. Start with the CMake-triggered Zig build and its xcodebuild -create-xcframework command; done means the ghostty-vt xcframework is generated and the full build completes successfully.
Written by the indexing model from the issue text.
Description
$ git log -1 --pretty=oneline
4611ac67cadf64a5706b9b9b928ff775f5309df0 (HEAD -> main, origin/main, origin/HEAD) Merge pull request #3 from mitchellh/push-ynozqtxqtoqp
$ zig version
0.15.2
$ cmake --version
cmake version 4.3.1
CMake suite maintained and supported by Kitware (kitware.com/cmake).
$ make clean build
rm -rf build
cmake -B build -DCMAKE_BUILD_TYPE=Release
-- The C compiler identification is AppleClang 17.0.0.17000603
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Found zig: /opt/homebrew/bin/zig
-- Configuring done (7.7s)
-- Generating done (0.0s)
-- Build files have been written to: /Users/omengue/go/src/github.com/mitchellh/go-libghostty/build
cmake --build build
gmake[1]: Entering directory '/Users/omengue/go/src/github.com/mitchellh/go-libghostty/build'
[100%] Building libghostty-vt via zig build...
install
└─ xcframework ghostty-vt failure
error: the following command exited with code 1 (expected exited with code 0):
xcodebuild -create-xcframework -library ./.zig-cache/o/651ac833a2581f54c078ef67427881f9/libghostty-vt.a -headers ./.zig-cache/o/9bc9de634b378ed19ead5f8a118a7266 -output /Users/omengue/go/src/github.com/mitchellh/go-libghostty/build/_deps/ghostty-src/zig-out/lib/ghostty-vt.xcframework
Build Summary: 56/58 steps succeeded; 1 failed
install transitive failure
└─ xcframework ghostty-vt failure
error: the following build command failed with exit code 1:
.zig-cache/o/0d2d2958d2bcd056603ca8f2bfa1f75d/build /opt/homebrew/Cellar/zig/0.15.2_1/bin/zig /opt/homebrew/Cellar/zig/0.15.2_1/lib/zig /Users/omengue/go/src/github.com/mitchellh/go-libghostty/build/_deps/ghostty-src .zig-cache /Users/omengue/.cache/zig --seed 0xe92902ea -Z939b7c6c467344e9 -Demit-lib-vt -Doptimize=ReleaseFast
gmake[3]: *** [_deps/ghostty-build/CMakeFiles/zig_build_lib_vt.dir/build.make:74: _deps/ghostty-src/zig-out/lib/libghostty-vt.0.1.0.dylib] Error 1
gmake[3]: *** Deleting file '_deps/ghostty-src/zig-out/lib/libghostty-vt.0.1.0.dylib'
gmake[2]: *** [CMakeFiles/Makefile2:107: _deps/ghostty-build/CMakeFiles/zig_build_lib_vt.dir/all] Error 2
gmake[1]: *** [Makefile:136: all] Error 2
gmake[1]: Leaving directory '/Users/omengue/go/src/github.com/mitchellh/go-libghostty/build'
make: *** [build/.ghostty-built] Error 2
- Dominant language
- Go
- Stars
- 157
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mitchellh/go-libghostty
-
Update for 1.4Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mitchellh/go-libghostty#20 ·
All issues in mitchellh/go-libghostty
Similar issues
-
agent-butler-finding chore
Difficulty 1/5 Under an hour Newbie friendliness 78/100
jordansmall/spindrift#6318 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Eyevinn/moqlivemock#166 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
JakeChampion/lang#14091 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
hyperledger/fabric-x-orderer#1409 ·
Maintainers usually reply within 3 days
-
get actions doesn't show the approval flag, and describe action shows it unformattedPossibly taken @kenokech claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day