HISE Logo Forum
    • Categories
    • Register
    • Login

    macOS Big Sur Xcode Compile Semantic Fail Errors

    Scheduled Pinned Locked Moved General Questions
    9 Posts 5 Posters 592 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.
    • K
      kameron
      last edited by

      When trying to compile HISE I'm experiencing the same issues in this thread:

      Link Preview Image
      Build fail - Semantics: "Reference to ‘Point’ is ambiguous"

      I’m trying to install HISE onto my Macbook Pro OS 10.15.4 (Catalina.) I’ve been following David’s video (which is really helpful!), I’ve installed the newes...

      favicon

      Forum (forum.hise.audio)

      Screen Shot 2021-10-24 at 9.22.25 PM.png

      I've read over this thread and checked all my projucer settings etc.
      I tried compiling the master and develop versions (develop version does not give me VST (Legacy) SDK Folder option in projucer btw)

      However, it seems the final solution for this thread was using Xcode 10.3

      My issue is I'm using a Macbook Pro M1, macOS Big Sur. Xcode 10.3 can not be used with macOS Big Sur. So, I have to use Xcode 13. I'm also using the latest version of Projucer 6.1.2.

      My question is, can I not compile HISE with Xcode 13? Or is there another solution for these errors?

      ustkU 1 Reply Last reply Reply Quote 0
      • ustkU
        ustk @kameron
        last edited by

        @kameron xcode 12.0 should work, although I'm not sure about M1 things...

        Can't help pressing F5 in the forum...

        1 Reply Last reply Reply Quote 0
        • ?
          A Former User
          last edited by A Former User

          I had similar issues this weekend!

          See here: https://forum.hise.audio/topic/4425/develop-branch-build-status/186

          Be sure to not compile the master branch but the new_layout! I am now compiling with XCode 13 on Big Sur... Works just fine...

          1 Reply Last reply Reply Quote 0
          • K
            kameron
            last edited by

            Thanks, I finally got it to work :)

            trillbillyT 1 Reply Last reply Reply Quote 0
            • trillbillyT
              trillbilly @kameron
              last edited by

              @kameron I also have to use Xcode 13. I bought a used Mac specifically for this and didn't realize they upgraded the OS to Monterey! Now I'm scrambling trying to get HISE going on here.

              How did you manage to get it compiled?

              K 1 Reply Last reply Reply Quote 0
              • K
                kameron
                last edited by

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • K
                  kameron @trillbilly
                  last edited by

                  @trillbilly

                  First, inside JUCE I unchecked all architectures except x86_64. Then set the deployment target to 10.4. The thread UrsBollhalder linked above has more info on this.

                  When I went to compile after this I got the errors I posted above.

                  To fix these errors I found out my issue was the branch I was trying to compile.

                  When I originally downloaded HISE I clicked the 'Download ZIP' button on the Github page. This zipped version kept giving me the errors.

                  I solved it by deleting that HISE folder. I then went back to Github and created an account and download the Github Desktop app.

                  After this I went to the HISE Github page and clicked Clone on Github Desktop instead of 'Download ZIP'. This cloned HISE to my Github Desktop App. From there I was able to download the new_layout branch.

                  The new_layout branch compiled for me without any errors with Xcode 13 on a new Macbook M1.

                  nouslouN 1 Reply Last reply Reply Quote 0
                  • nouslouN
                    nouslou @kameron
                    last edited by

                    @kameron Hi! Did you do that with enabled IPP?

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      kameron @nouslou
                      last edited by

                      @nouslou No I ended up disabling IPP.

                      I was getting IPP errors even though I had it installed. I haven't gone back to try to enable it yet

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

                      52

                      Online

                      1.7k

                      Users

                      11.7k

                      Topics

                      101.8k

                      Posts