Invalid JUCE Module Path when exporting

[weezycarter]

@d-healey Right, I exported as a standalone application but once the terminal says the process is complete I can't find an exported standalone application anywhere in my finder.

[d.healey]

@weezycarter Yes it should be in there if everything went well

[weezycarter]

@d-healey Should I recompile Hise and see if it does anything? I just compiled Hise about an hour ago following the youtube tutorial.

[d.healey]

@weezycarter I don't see how that would help. Your project is independent of HISE once you've clicked export. Are you able to run your compiled project from within xcode?

[weezycarter]

@d-healey How do I go about checking that.

[d.healey]

@weezycarter From projucer click save and open in IDE, then there should be a run button somewhere in xcode - I rarely use it so I'm not clear on the details of the interface.

[weezycarter]

@d-healey What file do I open in Projucer?
After exporting my project from Hise the terminal just runs with the "invalid Juce module path" message then when I go to my project folder under binaries, there is no compiled application file anywhere to be seen.

Sorry if i'm being redundant, i'm new to this program.

[d.healey]

@weezycarter said in Invalid JUCE Module Path when exporting:

After exporting my project from Hise the terminal just runs with the "invalid Juce module path"

Do you mean that the terminal actually opens Projucer and displays what you showed in the screenshot of your first post?

[weezycarter]

@d-healey

No the first screenshot was just me opening PowerJucer on my own to try to fix the path.

When I hit export in Hise a terminal opens that shows this

[d.healey]

@weezycarter Have you set the path to the HISE source code in HISE preferences?

[weezycarter]

@d-healey

Yes as far as I can tell

[d.healey]

@weezycarter

Uncheck this (I don't know if it will solve your problem, but you shouldn't need it).

[weezycarter]

@d-healey I unchecked it. I still don't see much difference.

When I hit export, the terminal runs with the message from my screenshot then when I look in my finder I can't find the exported application. The Compiled folder is blank.

[d.healey]

@weezycarter said in Invalid JUCE Module Path when exporting:

I look in my finder I can't find the exported application

The compilation never happens because of that error, so at this stage you won't see anything. We need to solve that error. I really don't know why you're seeing that error, the only module path that should matter is the User Modules one, and that is set correctly. Did you change any of them in Projucer?

[weezycarter]

@d-healey Nothing has changed in my projucer settings. My projucer settings can be seen in the first screenshot I posted.

[Christoph Hart]

@weezycarter The Path to JUCE looks wrong - it somehow points to the projucer itself. Point to the HISE/JUCE folder.

Have you used the Projucer before and changed anything in there?

[weezycarter]

@Christoph-Hart I pointed it to JUCE folder like you suggested and am still getting the same terminal error when exporting

[d.healey]

@weezycarter Try cleaning the build folder

[weezycarter]

@d-healey I hit Export>Clean Build Directory then I tried exporting again and got the same terminal message

[weezycarter]

@d-healey I might have to recompile Hise as It seems xcpretty gave me an error when trying to compile.

I don't know how to allow write permissions for that path its asking about.