交叉编译Qt5.1应用至AM1808 ARM平台时加载平台插件失败求助

Ah, I’ve run into this exact headache when moving from Qt4 to Qt5 on ARM targets—Qt5’s platform plugin system is way more strict than Qt4’s, which is almost certainly what’s tripping you up here. Let’s break down the fixes step by step:

• First, confirm your cross-compiled Qt5 includes the right platform plugins
  Unlike Qt4, which baked platform logic into core libraries, Qt5 splits this into separate plugins. Check your cross-compiled Qt5 installation directory (the one you set with -prefix during configure) for a plugins/platforms folder. You should see something like libqlinuxfb.so (for framebuffer setups) or libqxcb.so (if you’re using X11 on your AM1808). If this folder is empty or missing the correct plugin, you’ll need to recompile Qt5 with explicit platform support enabled—add -linuxfb or -qt-xcb to your configure command depending on your target setup.

• Deploy the platform plugin to the correct location on your AM1808
  Qt5 looks for platform plugins in specific spots by default:

  1. A platforms subdirectory in the same folder as your app binary
  2. The plugins/platforms folder under your Qt5 installation path on the target
  3. The path defined by the QT_QPA_PLATFORM_PLUGIN_PATH environment variable

  The quickest fix is to copy the entire platforms folder (with its .so plugin) into the same directory as your app. Alternatively, set the environment variable before launching your app:

  export QT_QPA_PLATFORM_PLUGIN_PATH=/path/to/your/app/platforms
  ./your_application
  

• Check for missing dependencies in the platform plugin
  Even if you have the plugin, it might fail to load if required libraries are missing. Use your cross-toolchain’s readelf to inspect dependencies:

  arm-2012.03/bin/arm-none-linux-gnueabi-readelf -d /path/to/libqlinuxfb.so
  

  Look for any NEEDED entries that aren’t present on your AM1808. Common missing libraries include libstdc++.so, libQt5Core.so, or other Qt5 core components—make sure these are deployed to /lib, /usr/lib, or included in your LD_LIBRARY_PATH.

• Explicitly specify the platform at launch
  Sometimes Qt5 can’t auto-detect the right platform, so forcing it via command line helps. Launch your app with the -platform flag matching your plugin:

  ./your_application -platform linuxfb
  

  (Swap linuxfb for xcb if you’re running X11 on the target.)

• Double-check your Qt5 cross-compile configuration
  Since your Qt4 app works, your toolchain and target environment are solid—so the issue is likely in how you configured Qt5. Compare your Qt4 configure flags to Qt5’s; Qt5 requires explicit platform flags that Qt4 enabled by default. For AM1808, a typical configure command might look like:

  ./configure -release \
    -prefix /opt/qt5-am1808 \
    -host-linux-g++ \
    -device linux-arm-gnueabi-g++ \
    -device-option CROSS_COMPILE=arm-2012.03/bin/arm-none-linux-gnueabi- \
    -linuxfb \
    -no-opengl \
    -opensource \
    -confirm-license
  

  Adjust the -device flag if a specific AM1808 configuration exists, and make sure you’re not missing any platform-related flags.

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