HISE Logo Forum
    • Categories
    • Register
    • Login

    Having trouble export an AUi

    Scheduled Pinned Locked Moved General Questions
    14 Posts 5 Posters 1.2k 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.
    • N
      noahcs @Dan Korneff
      last edited by

      @dustbro xcode 10.1

      1 Reply Last reply Reply Quote 0
      • Dan KorneffD
        Dan Korneff
        last edited by

        @noahcs said in Having trouble export an AUi:

        /Volumes/Noah's Ark/Hise Main/HISE-master/tools/Projucer/Projucer.app/Contents/MacOS/Projucer: No such file or directory

        Which HISE branch are you working from?
        I'm seeing:

        /Volumes/Noah's Ark/Hise Main/HISE-master/tools/Projucer/Projucer.app/Contents/MacOS/Projucer: No such file or directory
        

        The "master" branch is outdated and may be the cause of your issues. Download the latest Scripnode branch and try that.

        Dan Korneff - Producer / Mixer / Audio Nerd

        1 Reply Last reply Reply Quote 0
        • d.healeyD
          d.healey
          last edited by

          I just had this exact error today

          xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

          I gotta pop out but I'll post the solution when I'm back in about 30 mins

          Libre Wave - Freedom respecting instruments and effects
          My Patreon - HISE tutorials
          YouTube Channel - Public HISE tutorials

          1 Reply Last reply Reply Quote 0
          • N
            noahcs
            last edited by

            After downloading the scipnode patch ive got this:

            Last login: Mon Nov  9 14:46:10 on ttys001
            /Volumes/Noah\'s\ Ark/Hise\ Projects/Ferro/Binaries/batchCompileOSX ; exit;
            Noah-Sherrins-Macbook:~ noahsherrin$ /Volumes/Noah\'s\ Ark/Hise\ Projects/Ferro/Binaries/batchCompileOSX ; exit;
            /Volumes/Noah's Ark/Hise Projects/Ferro/Binaries/batchCompileOSX: line 2: /Volumes/Noah's Ark/Hise Main/HISE-develop/tools/Projucer/Projucer.app/Contents/MacOS/Projucer: No such file or directory
            Compiling Instrument plugin Ferro ...
            xcodebuild: error: 'Builds/MacOSX/Ferro.xcodeproj' does not exist.
            Compiling finished. Cleaning up...
            logout
            Saving session...
            ...copying shared history...
            ...saving history...truncating history files...
            ...completed.
            
            [Process completed]
            
            
            
            
            
            1 Reply Last reply Reply Quote 0
            • N
              noahcs
              last edited by

              *Scripnode Branch

              I was able to get rid of the error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance by following these instructions on retargeting xcode files

              "Now change the default developer tools directory with command:
              sudo xcode-select -s /Volumes/SSD/Applications/Xcode.app/Contents/Developer
              then do another zsh -lor restart the Terminal.app.

              After setting the Xcode.app as the default developer tools directory, run this command, to have Xcode figure itself out:
              /usr/bin/xcrun --find xcodebuild

              This took a little while, then I got back:
              /Volumes/SSD/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild"

              orangeO S 2 Replies Last reply Reply Quote 1
              • orangeO
                orange @noahcs
                last edited by orange

                @noahcs said in Having trouble export an AUi:

                *Scripnode Branch

                I was able to get rid of the error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance by following these instructions on retargeting xcode files

                "Now change the default developer tools directory with command:
                sudo xcode-select -s /Volumes/SSD/Applications/Xcode.app/Contents/Developer
                then do another zsh -lor restart the Terminal.app.

                After setting the Xcode.app as the default developer tools directory, run this command, to have Xcode figure itself out:
                /usr/bin/xcrun --find xcodebuild

                This took a little while, then I got back:
                /Volumes/SSD/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild"

                If you are using High Sierra, for Hise; I think XCode 8 would work much more stabile without these kind of errors and struggle.

                XCode 10 is smooth with Mojave and Catalina for Hise. (XCode 11 & 12 is not working properly with Hise also)

                develop Branch / XCode 13.1
                macOS Monterey / M1 Max

                N 1 Reply Last reply Reply Quote 0
                • N
                  noahcs @orange
                  last edited by

                  @orange Getting the same errors with XCode 8

                  1 Reply Last reply Reply Quote 0
                  • d.healeyD
                    d.healey
                    last edited by

                    line 2: /Volumes/Noah's Ark/Hise Main/HISE-develop/tools/Projucer/Projucer.app/Contents/MacOS/Projucer: No such file or directory

                    This is saying it can't find Projucer in the above location.

                    Libre Wave - Freedom respecting instruments and effects
                    My Patreon - HISE tutorials
                    YouTube Channel - Public HISE tutorials

                    1 Reply Last reply Reply Quote 0
                    • N
                      noahcs
                      last edited by

                      Finally fixed it! Turned out (as it normally is..) to be a very easy fix. Hise didn't like having the source code on an external HDD. All is good now, thanks to all that helped.

                      1 Reply Last reply Reply Quote 1
                      • S
                        Sawer @noahcs
                        last edited by

                        This post is deleted!
                        S 1 Reply Last reply Reply Quote 0
                        • S
                          Sawer @Sawer
                          last edited by

                          This post is deleted!
                          1 Reply Last reply Reply Quote 0
                          • d.healeyD d.healey referenced this topic on
                          • First post
                            Last post

                          16

                          Online

                          1.7k

                          Users

                          11.8k

                          Topics

                          102.5k

                          Posts