Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Special Interest Groups
  3. QtonPi
  4. Compiler setup & old style compile errors and warnings when using Pi EGLFS toolchain.
Forum Update on Tuesday, May 27th 2025

Compiler setup & old style compile errors and warnings when using Pi EGLFS toolchain.

Scheduled Pinned Locked Moved Unsolved QtonPi
3 Posts 2 Posters 747 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    robopoulos
    wrote on 1 Feb 2019, 20:59 last edited by
    #1

    I have the toolchain working pretty well on both RPi 2 & 3 for Qt 5.10.1. However, the toolchain default setup uses an old compiler gcc 4.8.3 for C which leads to lots of old compile errors and warnings unless one can follow coding standards before C99. What would be the guidelines to get a later compiler version?

    [ To avoid most of the old errors by getting to C99 std level one can use the following option in the .pro file:
    QMAKE_CFLAGS += -std=c99 This is not documented (?) but it works, while I can't get QMAKE_CXXFLAGS to work.]

    Thanx

    R 1 Reply Last reply 1 Feb 2019, 21:20
    0
    • R robopoulos
      1 Feb 2019, 20:59

      I have the toolchain working pretty well on both RPi 2 & 3 for Qt 5.10.1. However, the toolchain default setup uses an old compiler gcc 4.8.3 for C which leads to lots of old compile errors and warnings unless one can follow coding standards before C99. What would be the guidelines to get a later compiler version?

      [ To avoid most of the old errors by getting to C99 std level one can use the following option in the .pro file:
      QMAKE_CFLAGS += -std=c99 This is not documented (?) but it works, while I can't get QMAKE_CXXFLAGS to work.]

      Thanx

      R Offline
      R Offline
      robopoulos
      wrote on 1 Feb 2019, 21:20 last edited by robopoulos 2 Jan 2019, 21:37
      #2

      Hmm, why didn't I test this then. Rather use

      QMAKE_CFLAGS= gcc -std=c11

      sorry, late night errors, should be: QMAKE_CFLAGS += -std=c11

      to get up to C11 level with gcc 4.8.3 compiler.

      [Cxx flags are for C++ I assume, so that is why they do not affect C ?]

      A 1 Reply Last reply 2 Feb 2019, 06:02
      1
      • R robopoulos
        1 Feb 2019, 21:20

        Hmm, why didn't I test this then. Rather use

        QMAKE_CFLAGS= gcc -std=c11

        sorry, late night errors, should be: QMAKE_CFLAGS += -std=c11

        to get up to C11 level with gcc 4.8.3 compiler.

        [Cxx flags are for C++ I assume, so that is why they do not affect C ?]

        A Offline
        A Offline
        aha_1980
        Lifetime Qt Champion
        wrote on 2 Feb 2019, 06:02 last edited by
        #3

        @robopoulos

        [Cxx flags are for C++ I assume, so that is why they do not affect C ?]

        Correct.

        Qt has to stay free or it will die.

        1 Reply Last reply
        0

        3/3

        2 Feb 2019, 06:02

        • Login

        • Login or register to search.
        3 out of 3
        • First post
          3/3
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved