Uploaded image for project: 'Qt for Python'
  1. Qt for Python
  2. PYSIDE-1032

Incorrect SDK paths leading to compiler not finding `string.h` in PySide2 build

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P2: Important
    • Resolution: Fixed
    • Affects Version/s: 5.12.4
    • Fix Version/s: 5.12.5, 5.13.1
    • Component/s: PySide
    • Labels:
      None
    • Environment:
      macOS 10.14.5 Mojave, Xcode 10.2.1, SDK 10.14, Cmake 3.14.4, clang 7, Qt 5.12.4
    • Platform/s:
      macOS
    • Commits:
      992ff1f7925009b7ead6d6f005cafcf2e57ed44e (pyside/pyside-setup/5.12)

      Description

      Upon finishing build of shiboken2 and moving on to pyside2, clang fails to find string.h:

      [  0%] Building CXX object plugins/CMakeFiles/uiplugin.dir/customwidgets.cpp.o
      (core) clang_parseTranslationUnit2(0x0, cmd[14]=-nostdinc -isystem/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1 -isystem/usr/local/include -isystem/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/10.0.1/include -isystem/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include -iframework/System/Library/Frameworks -iframework/Library/Frameworks -fPIC -Wno-expansion-to-defined -Wno-constant-logical-operand -std=c++14 -I/Users/kkyzivat/Build/Autodesk/pyside-setup/sources/pyside2/PySide2 -I/Users/kkyzivat/Build/Autodesk/pyside-setup/workdir/artifactory/qt_5.12.4/include /private/var/folders/hb/l5gg_s816gd15sl9_dk9hvpw0000gn/T/QtCore_global_kEygzw.hpp)
      /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/string.h:61:15: fatal error: 'string.h' file not found
      

      Previous build of PySide ~5.12.2 from commit sha 0fc54b0 was successful, building shiboken2 and pyside2 successfully..
      Current build of PySide at tip of 5.12.4 branch (commit sha b140239 fails with the above failure.

      The machine and environment have not changed between builds of these two SHAs.

      A git bisect lead to f4d1a606a0fe5f15ea89779ca3f1bbb9673c2cc6 being the culprit.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            • Assignee:
              crmaurei Cristian Maureira-Fredes
              Reporter:
              kkyzivat Keith Kyzivat
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes