HISE Logo Forum
    • Categories
    • Register
    • Login

    Compile error macOS Tahoe: error Cycle inside a single target

    Scheduled Pinned Locked Moved General Questions
    3 Posts 2 Posters 195 Views
    Loading More Posts
    • 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.
    • D
      Daanyoo
      last edited by Daanyoo

      Re: ERROR: Cycle inside a single target

      Hello everyone,

      as I already upgraded to macOS Tahoe recently I was hoping to be able to go through the compilation process of my VSTi plugin as I have been before. Unfortunately I'm getting the same error as mentioned in the referenced thread..

      ⚠️ Building targets in manual order is deprecated - check "Parallelize build for command-line builds" in the project editor, or set DISABLE_MANUAL_TARGET_ORDER_BUILD_WARNING in any of the targets in the current build to suppress this warning
      note: Target dependency graph (3 targets)
      ❌ error: Cycle inside a single target; building could produce unreliable results.
      ** BUILD FAILED **

      Standalone Export goes through just fine...

      @Christoph-Hart One thing I noticed in the previous thread was a message from Christoph implementing a fix regarding the Copy Step - he then committed a fix, which should hold until macOS 20
      Now we made the jump to macOS 26^^ so this is the reminder haha

      I'm on the latest commit of the development branch and already tried downgrading to xcode 16.4, both unfortunately not working...

      Any help is greatly appreciated!

      Christoph HartC 1 Reply Last reply Reply Quote 0
      • Christoph HartC
        Christoph Hart @Daanyoo
        last edited by

        @Daanyoo haha you're right, I was this close telling you to use another Xcode version but then I remembered that commit in question.

        It's exactly like you said: they bumped the version to 26, so my check whether Sonoma or later is present failed because I only did this until 20...

        I'm looking forward to be reminded again next year when the next version comes out. I mean I could assume that the next version number is 27 and write a bunch of code that will make it work with the next versions, but look where that got us here...

        D 1 Reply Last reply Reply Quote 2
        • D
          Daanyoo @Christoph Hart
          last edited by

          @Christoph-Hart haha, absolute madness from Apple, no one could have expected such an unnecessary change
          thank you for the quick fix, that was indeed the solution - now the export runs just fine! you saved me from downgrading my OS again^^

          Lets see when I will encounter my next bug with this new macOS update...

          1 Reply Last reply Reply Quote 0
          • First post
            Last post

          22

          Online

          2.0k

          Users

          12.6k

          Topics

          109.5k

          Posts