Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Major compilation problem (after updating to macOS Sonoma 14.5?)
Forum Updated to NodeBB v4.3 + New Features

Major compilation problem (after updating to macOS Sonoma 14.5?)

Scheduled Pinned Locked Moved Solved General and Desktop
4 Posts 3 Posters 1.2k Views 1 Watching
  • 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.
  • MortyMarsM Offline
    MortyMarsM Offline
    MortyMars
    wrote on last edited by
    #1

    Hi everyone,

    After a few days of rest for my project (and also after upgrading macOS to Sonoma 14.5 -I was using 14.4.1 before-, which may have something to do with my problem) I can't compile any more.
    I get two error messages when compiling:

    1. "No rule to make target `Procedures4XP'. Stop."

    2. "/Applications/Qt/6.7.0/macos/mkspecs/features/mac/sdk.mk:24: error : *** ^. Stop."

    This takes me to the following code in the editor:

    ifeq ($(QT_MAC_SDK_NO_VERSION_CHECK),)
        CHECK_SDK_COMMAND = /usr/bin/xcrun --sdk $(EXPORT_QMAKE_MAC_SDK) -show-sdk-version 2>/dev/null
        CURRENT_MAC_SDK_VERSION := $(shell DEVELOPER_DIR=$(EXPORT_QMAKE_XCODE_DEVELOPER_PATH) $(CHECK_SDK_COMMAND))
        ifneq ($(CURRENT_MAC_SDK_VERSION),$(EXPORT_QMAKE_MAC_SDK_VERSION))
            # We don't want to complain about out of date SDK unless the target needs to be remade.
            # This covers use-cases such as running 'make check' after moving the build to a
            # computer without Xcode or with a different Xcode version.
            TARGET_UP_TO_DATE := $(shell QT_MAC_SDK_NO_VERSION_CHECK=1 $(MAKE) --question $(QMAKE_TARGET) && echo 1 || echo 0)
            ifeq ($(TARGET_UP_TO_DATE),0)
                ifneq ($(findstring missing DEVELOPER_DIR path,$(CURRENT_MAC_SDK_VERSION)),)
                    $(info The developer dir $(EXPORT_QMAKE_XCODE_DEVELOPER_PATH) is no longer valid.)
                else ifneq ($(findstring SDK "$(EXPORT_QMAKE_MAC_SDK)" cannot be located,$(CURRENT_MAC_SDK_VERSION)),)
                    $(info The developer dir $(EXPORT_QMAKE_XCODE_DEVELOPER_PATH) no longer contains the $(EXPORT_QMAKE_MAC_SDK_VERSION) platform SDK.)
                else ifneq ($(CURRENT_MAC_SDK_VERSION),)
                    $(info The $(EXPORT_QMAKE_MAC_SDK) platform SDK has been changed from version $(EXPORT_QMAKE_MAC_SDK_VERSION) to version $(CURRENT_MAC_SDK_VERSION).)
                else
                    $(info Unknown error resolving current platform SDK version.)
                endif
                $(info This requires a fresh build of your project. Please wipe the build directory)
                ifneq ($(EXPORT__QMAKE_STASH_),)
                    $(info including the qmake cache in $(EXPORT__QMAKE_STASH_))
                endif
                $(error ^)
            endif
        endif
    endif
    
    

    And in each of my .h or .cpp files, the code editor reports references not found:

    approchwindow.h:4:10: In included file: 'type_traits' file not found
    qglobal.h:13:12: error occurred here
    approchwindow.h:27:31: In template: no type named 'parameter_type' in 'QArrayDataPointer<QList<QLabel >>'
    qlist.h:100:28: error occurred here
    Cannot initialize a parameter of type 'QMainWindow ' with an rvalue of type 'ApprochWindow '

    I don't understand what's happening when a few days ago everything was compiling without a hitch.

    Below is a screenshot of the extent of the problems, I don't know what to do to get the project back up and running...

    Capture d’écran 2024-05-18 à 02.06.17.jpg

    I hope that this will suggest a solution to someone.

    Thank you for your help

    1 Reply Last reply
    0
    • hskoglundH Offline
      hskoglundH Offline
      hskoglund
      wrote on last edited by
      #2

      I also had problems after updating, but after erasing all build directories and cmake.txt.users projects files it was smooth sailing again.

      N 1 Reply Last reply
      2
      • MortyMarsM Offline
        MortyMarsM Offline
        MortyMars
        wrote on last edited by
        #3

        Thank you very much @hskoglund, it's working again !
        You've just saved my day... my week... ;-)

        1 Reply Last reply
        0
        • MortyMarsM MortyMars has marked this topic as solved on
        • hskoglundH hskoglund

          I also had problems after updating, but after erasing all build directories and cmake.txt.users projects files it was smooth sailing again.

          N Offline
          N Offline
          Neil Sagar Sahu
          wrote on last edited by
          #4

          @hskoglund Hello there, can you help me with the process such that my .cpp files and .h files get executed properly ?

          1 Reply Last reply
          0

          • Login

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