Uploaded image for project: 'Qt for MCUs'
  1. Qt for MCUs
  2. QTMCU-2

Bundled Example Projects Do Not Build

    XMLWordPrintable

Details

    • Windows

    Description

      With Qt for MCUs  1.2.0, the bundled examples do not build out of the box. This is a fresh installation of Windows 10 x64. There are no other installations of Qt on the system. I installed all software using the Qt installer.

      Some problems I encountered:

      • Installing the Ninja tool through the Qt Installer does not make it available to CMake, even when run through QtCreator. Instead, you have to manually add add the directory containing the Ninja executable to the PATH environment variable. The error message around this is a little cryptic, though I'm having trouble reproducing it.
      • Once Qt for MCUs is installed to a fresh Qt Installation folder, and QtCreator is launched, I was presented with the "Welcome" screen with several example projects. After clicking on the example projects, the Projects tab on the sidebar says "The project was not parsed successfully." Even after changing the build directory to a directory that exists, the message persists. I cannot find any information about what this means or how to fix it.
      • The installed toolchain by default generates the message "C and C++ compiler paths differ. C compiler may not work". The C compiler is C:/QtMcu/Tools/QtMCUs/arm_gcc_8/bin/arm-none-eabi-gcc.exe and the C++ compiler is C:/QtMcu/Tools/QtMCUs/arm_gcc_8/bin/arm-none-eabi-g+.exe. Those seem to be the appropriate compilers, and I can't select +g++ for the C compiler so I'm not sure how to resolve this error message.
      • CMake generates a Ninja script which includes the linker flags --major-image-version and --minor-image-version. The provided linker fails because it does not recognize these flags. I removed the lines from C:\QtMcu\Tools\Cmake_64\share\cmake-3.17\Modules\Platform\Windows-GNU.cmake. This allowed the build to proceed to the next problem:
      • The linker fails because "exit.c: (.text.exit+0x2c): undefined reference to `_exit'". I'm not sure how to go about defining that symbol, but I'd assume that would probably be provided by the BSP.

      Attachments

        1. image-2020-06-25-11-00-12-346.png
          78 kB
          Yoann Lopes
        2. image-2020-06-25-16-02-54-588.png
          154 kB
          Wes Waugh
        3. image-2020-06-25-16-17-23-553.png
          59 kB
          Wes Waugh
        4. image-2020-06-25-16-18-41-800.png
          179 kB
          Wes Waugh
        5. image-2020-06-25-16-23-49-001.png
          120 kB
          Wes Waugh
        6. image-2020-06-25-16-28-33-767.png
          184 kB
          Wes Waugh
        7. image-2020-06-25-16-29-24-762.png
          216 kB
          Wes Waugh
        8. image-2020-06-26-15-27-04-391.png
          190 kB
          Alessandro Portale
        9. screenshot-1.png
          80 kB
          Wes Waugh

        Activity

          People

            Unassigned Unassigned
            wes219design Wes Waugh
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: