在macOS上用mingw-w64交叉编译带CGO 1.10的Go程序至Windows

Got it, let's work through this cross-compilation issue step by step. You’ve already knocked out the hard part with compiling ZXing, your custom C++ code, and building the static library—so we just need to make sure Go’s CGO toolchain is properly wired up to use that library when targeting Windows.

1. Set Up Go Cross-Compilation Environment Variables First #

First, you need to tell Go to target Windows and use the MinGW-w64 toolchain for CGO. Run these commands in your terminal to set the required environment variables:

export GOOS=windows
export GOARCH=amd64
export CGO_ENABLED=1
export CC=x86_64-w64-mingw32-gcc
export CXX=x86_64-w64-mingw32-g++

Note: On Apple Silicon Macs, double-check that Homebrew installed MinGW-w64 in /opt/homebrew/opt/mingw-w64/bin—if your tools aren’t found, add that path to your $PATH first.

2. Fix CGO Pragmas in Your Go Code #

Your Go file that calls the C++ function needs explicit #cgo directives to point to your headers and static library. Make sure it looks something like this:

package qrcode

/*
#cgo CFLAGS: -I./path/to/zxing-headers -I./path/to/your-custom-headers
#cgo LDFLAGS: -L./path/to/your-static-library -lzxingqr -lstdc++ -lm
#include "qrcode.h"
*/
import "C"

// SimpleQRDecode wraps the C++ FindAndDecodeQR function
func SimpleQRDecode(imagePath string) string {
    // Your Go wrapper code here
}

Critical details here:

• Replace the paths with your actual header/library locations
• The -lstdc++ flag is mandatory because you’re linking C++ code
• -lm covers any math dependencies from ZXing

3. Verify Your C++ Header Uses extern "C" #

If you’re seeing "undefined reference" errors for FindAndDecodeQR, it’s almost certainly because C++ name mangling is breaking Go’s ability to find the function. Your qrcode.h must wrap the function declaration in extern "C":

#ifndef QRCODE_H
#define QRCODE_H

#ifdef __cplusplus
extern "C" {
#endif

// Declare the function with C-style linkage
const char* FindAndDecodeQR(const char* imagePath);

#ifdef __cplusplus
}
#endif

#endif

4. Build Your Go Program with Correct Linker Flags #

When you run the Go build command, confirm you’re passing the right linker flags (or rely on the #cgo directives above). A working build command would look like:

go build -o qrdecoder.exe ./your-main-package

If you want to override or add flags explicitly:

go build -o qrdecoder.exe -ldflags="-L./libs -lzxingqr -lstdc++ -lm" ./your-main-package

5. Debug Linker Issues with Verbose Output #

If you’re still hitting errors, run the build with the -x flag to see exactly what commands Go is executing. This will show you if the MinGW linker is being called correctly and if your library paths are right:

go build -x -o qrdecoder.exe ./your-main-package

6. Validate Your Static Library Has the Right Symbols #

Double-check that your static library actually contains the unmangled FindAndDecodeQR symbol using MinGW’s nm tool:

x86_64-w64-mingw32-nm libzxingqr.a | grep FindAndDecodeQR

You should see output like 00000000 T FindAndDecodeQR. If you get a mangled name (e.g., _Z16FindAndDecodeQRPKc), go back and fix the extern "C" wrapping in your header.

内容的提问来源于stack exchange，提问作者The Architect