HISE Logo Forum
    • Categories
    • Register
    • Login

    URGENT:: Building is failed with xcpretty.

    Scheduled Pinned Locked Moved General Questions
    4 Posts 2 Posters 2.3k 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.
    • Evan C.E
      Evan C.
      last edited by

      Hello,
      I am just trying to export an AUi plugin on HISE, but it is failing again and again.

      ..../HISE Project/Binaries/batchCompileOSX: line 5: xcpretty: command not found
      

      I tried to pull the recent source of HISE and build HISE standalone again.
      I can't know what I have to do to resolve this issue.
      Please help me.

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

        You have to install xcpretty, a ruby gem that transforms the bullshit output from the xcode commandline compiler to something human readable.

        Installation is pretty easy:

        Link Preview Image
        xcpretty/README.md at master · xcpretty/xcpretty

        Flexible and fast xcodebuild formatter. Contribute to xcpretty/xcpretty development by creating an account on GitHub.

        favicon

        GitHub (github.com)

        1 Reply Last reply Reply Quote 1
        • Evan C.E
          Evan C.
          last edited by

          Thanks.

          And now I am getting following error messages.

          /Volumes/Work/HISE/HISE/hi_frontend/frontend/FrontendProcessorEditor.cpp:403:37: no member named 'unlocker' in 'FrontendProcessor'
          
                              TurboActivateUnlocker* ul = &fp->unlocker;
                                                           ~~  ^
          
          1 Reply Last reply Reply Quote 0
          • Christoph HartC
            Christoph Hart
            last edited by

            Ah I forgot to hide this behind the USE_TURBO_ACTIVATE macro. I just committed the fix. I checked and the demo_project builds successfully as Standalone on OS X.

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

            34

            Online

            1.7k

            Users

            11.7k

            Topics

            102.0k

            Posts