Uploaded image for project: 'Qbs ("Cubes")'
  1. Qbs ("Cubes")
  2. QBS-922

Fails compiling BareMetal project

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P2: Important
    • 1.5.0
    • 1.4.4
    • General
    • None
    • Windows 10 64bit and Xubuntu 14.10
    • f461da30b54fae1c4c23279a183b1715aee4ecef

    Description

      After I upgraded to the new Qt Creator 3.6.0 I'm not able to compile a BareMetal project using arm gcc either using windows or linux.

      Here is the error message:
      19:18:45: Running steps for project blinky_template...
      compiling nrf_soc.c
      compiling nrf_assert.c
      compiling system_nrf51.c
      compiling app_error.c
      The process '/usr/bin/arm-none-eabi-gcc.out' could not be started: No such file or directory. The full command line invocation was: /usr/bin/arm-none-eabi-gcc.out -g -O0 -pipe -fvisibility=default -mcpu=cortex-m0 -mthumb -mabi=aapcs -mfloat-abi=soft -std=gnu99 -fno-builtin -fdata-sections -ffunction-sections -fno-strict-aliasing -Wall -DDEBUG -DNRF51 -DBOARD_BLE400 -DBSP_DEFINES_ONLY -DBUILD_NUM=0001 -DBOARD_REV=1 -I/home/raivis/QtProjects/nrf_blinky_example -I/home/raivis/QtProjects/nrf_blinky_example/config -I/home/raivis/QtProjects/nrf_blinky_example/drivers -I/home/raivis/QtProjects/sdk_10/examples/bsp -I/home/raivis/QtProjects/sdk_10/external/freertos/config -I/home/raivis/QtProjects/sdk_10/external/freertos/portable/GCC/nrf51 -I/home/raivis/QtProjects/sdk_10/external/freertos/portable/CMSIS/nrf51 -I/home/raivis/QtProjects/sdk_10/external/freertos/source/include -I/home/raivis/QtProjects/sdk_10/components/device -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/config -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/hal -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/common -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/nrf_soc_nosd -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/clock -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/uart -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/timer -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/ppi -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/gpiote -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/rng -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/rtc -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/spi_master -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/spi_slave -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/twi_master -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/wdt -I/home/raivis/QtProjects/sdk_10/components/drivers_nrf/delay -I/home/raivis/QtProjects/sdk_10/components/libraries/util -I/home/raivis/QtProjects/sdk_10/components/libraries/uart -I/home/raivis/QtProjects/sdk_10/components/libraries/fifo -I/home/raivis/QtProjects/sdk_10/components/libraries/pwm -I/home/raivis/QtProjects/sdk_10/components/libraries/twi -I/home/raivis/QtProjects/sdk_10/components/toolchain -I/home/raivis/QtProjects/sdk_10/components/toolchain/gcc -c /home/raivis/QtProjects/sdk_10/components/drivers_nrf/nrf_soc_nosd/nrf_soc.c -o /home/raivis/QtProjects/build-blinky_template-nrf51822-Debug/qtc_nrf51822_f061a8e7-debug/blinky.qtc-nrf51822-f061a8e7.f0e7c8ab/.obj/96be494cc2b318aa/nrf_soc.c.o
      The following products could not be built for configuration qtc_nrf51822_f061a8e7-debug:
      blinky
      Error while building/deploying project blinky_template (kit: nrf51822)
      When executing step "Qbs Build"
      19:18:45: Elapsed time: 00:00.

      I noticed that for some odd reason Qt Creator is trying to execute arm-none-eabi-gcc.out, which I believe is not correct and why would it suddenly try to run a command with .out suffix? The same happens on windows.

      So Just to see whether that is the case, on linux I made symbolic link to the arm-gcc-none-eabi executable with "out" suffix. And it now works. However, I'm not sure if I can do something similar on windows machine, since I don't have symlinks

      It's also interesting that it compiles some of the files before failing, and the file it fails seems to be determined randomly.

      I added some screenshots of my configuration and qbs file of my sample project. Hopefully I was able to give good enough description to understand what is the issue.

      Best Regards
      Raivis Strogonovs

      Attachments

        1. blinky_template.qbs
          12 kB
        2. kits.png
          kits.png
          59 kB
        3. qt_creator_issue_2.png
          qt_creator_issue_2.png
          86 kB
        4. qt_creator_issue_3.png
          qt_creator_issue_3.png
          120 kB
        5. qt_creator_issue_4.png
          qt_creator_issue_4.png
          266 kB
        6. qt_creator_issue_now_works.png
          qt_creator_issue_now_works.png
          236 kB
        7. qt_creator_issue_symlink.png
          qt_creator_issue_symlink.png
          131 kB
        8. qt_creator_issue.png
          qt_creator_issue.png
          87 kB
        For Gerrit Dashboard: QBS-922
        # Subject Branch Project Status CR V

        Activity

          People

            kandeler Christian Kandeler
            xcoder Raivis Strogonovs
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes