xcpretty Not Detected After Install on macOS Tahoe M1: Compiling Fails in HISE Export

[David Healey]

@DJJD12345 I'm guessing it's reading configuration files from a previous time when you ran Projucer. Is that Projucer v6.1.3?

[DJJD12345]

@David-Healey yes, should I use juce module folder in Hise source foler or the one that can with the latest version of juce

[DJJD12345]

@David-Healey It's Juce 6.1.4 that Hise uses, not 6.1.3

[David Healey]

@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.

[DJJD12345]

@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

[David Healey]

@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

[DJJD12345]

@David-Healey What do you mean by "../../"?

[David Healey]

@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.

[DJJD12345]

@David-Healey No, for the global path to Juce and the juice modules.

[David Healey]

@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

[DJJD12345]

This post is deleted!

[DJJD12345]

@David-Healey You're on Linux; show me what the global paths look like on Mac

[DJJD12345]

@David-Healey, this is what my global path looks like for Juce.

[David Healey]

@DJJD12345

This is what I have on Mac but the global paths aren't used in the module settings. You can also disable the checkbox "Warn about incorrect JUCE path"

[DJJD12345]

@David-Healey Still get error message of incorrect path for juce for global path when I try to save and open with IDE

[David Healey]

@DJJD12345 Did you disable the checkbox? What are your individual module paths set to?

[DJJD12345]

@David-Healey Path to juce /Documents/HISE/JUCE
And for modules /Documents/HISE/JUSE/modules

[David Healey]

@DJJD12345 Ok, set them as I showed you above. ../../ etc.

[DJJD12345]

@David-Healey For the VST SDK path in global path for JUCE is /Documents/HISE/tools/SDK
and did what you said to put the global path as and modules path is red now, but juce path is not. But doing ../../JUCE for the path to juce makes the text red

[David Healey]

@DJJD12345 In the global paths dialog click the reset to defaults button.

@DJJD12345 said in xcpretty Not Detected After Install on macOS Tahoe M1: Compiling Fails in HISE Export:

and did what you said to put the global path as and modules path is red now, but juce path is not. But doing ../../JUCE for the path to juce makes the text red

Can you show me a screenshot?