从Mac交叉编译Qt到Raspbian Stretch(RPi3)时遇问题求助

Hey there, I’ve wrestled through the exact same cross-compiling headaches with Qt for Raspberry Pi on Mac before—so I totally feel your frustration! Let’s break down the most common pitfalls that trip people up at step 10 of that guide, since that’s usually where toolchain or environment setup cracks start showing.

First, let’s assume you’re running the qmake command with the Raspberry Pi spec file as outlined. Here are the top fixes to try:

• Double-check your toolchain paths and environment variables
  MacOS has weird quirks with path resolution, especially if you installed the cross-compiler via Homebrew or a custom location. Run echo $CC and echo $CXX to confirm they point directly to your arm-linux-gnueabihf-gcc and arm-linux-gnueabihf-g++ binaries. If not, export them explicitly before running qmake:

  export CC=/path/to/your/toolchain/bin/arm-linux-gnueabihf-gcc
  export CXX=/path/to/your/toolchain/bin/arm-linux-gnueabihf-g++
  

  Also, make sure the toolchain’s bin directory is in your PATH—run echo $PATH to verify it’s listed.

• Fix a glitchy sysroot mount
  If you used sshfs to mount the Pi’s root filesystem (as the guide suggests), MacOS’s FUSE implementation often flaks out. Unmount it with umount /path/to/sysroot then remount with explicit permissions to avoid access issues:

  sshfs pi@your-pi-ip:/ /path/to/sysroot -o allow_other,defer_permissions
  

  Double-check you can navigate to /path/to/sysroot/usr/include and see the Pi’s header files—if it’s empty or throws an error, the mount is definitely your problem.

• Correct mismatched qmake spec file settings
  The default linux-rasp-pi2-g++ spec file sometimes has hardcoded paths that don’t match your setup. Open the file (usually in qtbase/mkspecs/linux-rasp-pi2-g++/qmake.conf) and verify:

  • QMAKE_CC and QMAKE_CXX point to your cross-compiler
  • QMAKE_SYSROOT is set to your mounted sysroot path
  • QMAKE_LIBDIR_QT points to the correct Qt libs on the Pi or your local build directory

• Avoid MacOS library conflicts
  MacOS ships with its own versions of libraries like libssl or libz that can leak into cross-compilation and cause errors. Try running qmake in a clean environment to block these system libs:

  env -i PATH=$PATH CC=$CC CXX=$CXX qmake /path/to/your/project.pro -spec linux-rasp-pi2-g++
  

• Update your tools
  Outdated cross-compilers or Qt source versions are a common culprit. If you used Homebrew to install the toolchain, run brew upgrade arm-linux-gnueabihf-gcc to get the latest version. For Qt, stick to 5.15+—it’s the most stable for Raspberry Pi 2 EGLFS setups.

If you can share the exact error message you’re hitting, we can narrow this down even further—but these steps fix 90% of the issues I’ve seen at this stage.

内容的提问来源于stack exchange，提问作者Jordan Violet