@@ -94,13 +94,16 @@ jobs:
9494 ls -la .cargo/bin
9595
9696 - name : Test protoc-gen-go availability
97+ id : protoc_gen_go_setup
9798 shell : bash
9899 run : |
99100 echo "Current PATH: $PATH"
100101 echo "Go bin directory contents:"
101102 ls -la $HOME/go/bin/
102103 echo "Which protoc-gen-go:"
103- which protoc-gen-go
104+ PROTOC_GEN_GO_PATH=$(which protoc-gen-go)
105+ echo "Found protoc-gen-go at: $PROTOC_GEN_GO_PATH"
106+ echo "protoc_gen_go_path=$PROTOC_GEN_GO_PATH" >> $GITHUB_OUTPUT
104107 echo "Testing protoc can find protoc-gen-go plugin..."
105108 # Test that protoc can find the go plugin (this will show an error about missing .proto file, but that's expected)
106109 protoc --go_out=/tmp --help | grep -q "go_out" && echo "✅ protoc recognizes --go_out flag" || echo "❌ protoc does not recognize --go_out flag"
@@ -148,11 +151,12 @@ jobs:
148151 - name : Build CFFI Library
149152 shell : bash
150153 env :
151- PROTOC_GEN_GO_PATH : /home/runner/go/bin/protoc-gen-go
154+ PROTOC_GEN_GO_PATH : ${{ steps.protoc_gen_go_setup.outputs.protoc_gen_go_path }}
152155 run : |
156+ echo "Using PROTOC_GEN_GO_PATH: $PROTOC_GEN_GO_PATH"
153157 # We must use PROTOC_GEN_GO_PATH to explicitly tell the build script
154158 # where to find the plugin, as the cross-compile environment is isolated.
155- ${{ env.CARGO }} build --release -p baml_cffi ${{ env.TARGET_FLAGS }}
159+ ${{ env.CARGO }} build --debug -p baml_cffi ${{ env.TARGET_FLAGS }}
156160 working-directory : engine
157161 # Skip this step on Windows runners
158162 if : matrix._.os != 'windows-2022'
0 commit comments