xcpretty Not Detected After Install on macOS Tahoe M1: Compiling Fails in HISE Export
-
@David-Healey
What do you mean by "has been customized"? -
@DJJD12345 said in xcpretty Not Detected After Install on macOS Tahoe M1: Compiling Fails in HISE Export:
What do you mean by "has been customized"?
Christoph has modified it, that's why it's included with the HISE source code.
-
@David-Healey What's different about it than the latest version, and why can't he use the newest version but customize it
-
@DJJD12345 said in xcpretty Not Detected After Install on macOS Tahoe M1: Compiling Fails in HISE Export:
What's different about it than the latest version, and why can't he use the newest version but customize it
I don't know what all the differences are.
There are licensing issues with recent versions of JUCE preventing an update. It doesn't prevent you from using the latest version though for other non-HISE projects, but for HISE you need to stick with what's included in the git repo.
-
@David-Healey I used Xcode to clone the Hise source code from the dev branch and installed Faust 2.81.10, and then deleted all versions of Hise and redownloaded Hise and set the Hise source code path to where I installed it. Here is the video of me compiling Hise (Here is the link as a google drive link cuz the file size it too big https://drive.google.com/file/d/12PAYn1xIMnOnxtmhC7FFDIBF__rQHljX/view?usp=sharing). I downloaded Faust 2.81.10 as shown in the video, and it won't let me compile with Faust.
-
@DJJD12345 Thanks, watching now
-
@David-Healey is there anything I did incorrectly?
-
@DJJD12345 You're doing some stuff in Projucer that isn't necessary.
Please watch the compiling HISE section of the bootcamp and follow all of the steps I show. Do exactly as I do, don't do anything different.
-
@David-Healey juce said this while saving compiling settings
-
@DJJD12345 I'm guessing it's reading configuration files from a previous time when you ran Projucer. Is that Projucer v6.1.3?
-
@David-Healey yes, should I use juce module folder in Hise source foler or the one that can with the latest version of juce
-
@David-Healey It's Juce 6.1.4 that Hise uses, not 6.1.3
-
@DJJD12345 Ah yes I think on Mac it is 6.1.4.
@DJJD12345 said in xcpretty Not Detected After Install on macOS Tahoe M1: Compiling Fails in HISE Export:
@David-Healey yes, should I use juce module folder in Hise source foler or the one that can with the latest version of juce
Only use what's included with the HISE source code. If you have another version it's possible that its config files are interfering and that's why you are seeing missing path errors.
-
@David-Healey Did that and said modules couldn't be found when the projucer path is set to the one in Hise source code, as well as the path to the JUCE modules
-
@DJJD12345 said in xcpretty Not Detected After Install on macOS Tahoe M1: Compiling Fails in HISE Export:
Did that and said modules couldn't be found when the projucer path is set to the one in Hise source code, as well as the path to the JUCE modules
For the HISE modules the paths should be set to
../../
For the JUCE modules the should be
../../JUCE/modules
-
@David-Healey What do you mean by "../../"?
-
@DJJD12345 That's what you need to put in those boxes if it's not there already.
../means one directory up from the current directory,../../means two directories up. -
@David-Healey No, for the global path to Juce and the juice modules.
-
@DJJD12345 Don't use the global paths.
This is what my global paths window looks like
But the checkbox is not enabled for the modules
-
This post is deleted!
