JUCE submodule PSA

[David Healey]

@Christoph-Hart said in JUCE submodule PSA:

@David-Healey can you check if it works now? I've recompiled the Projucer in both JUCE branches and it should now compile & export, but I'm running against the funky SimdRegister error here (BTW, have you fixed that on your HISE branch?).

I'll give it a try.

That invalid use of incomplete type error never showed up my fork. It only happens upstream. I can't see any difference in the lines of code related to it between upstream and my fork so it's had me scratching my head. The only thing I can think is that the order that files are being included is somehow different, but I'm really not sure.

I did add this PR to fix the symptom. The error first showed up with this commit.

Edit: Interesting, I've just pulled in the latest changes and my branch has now inherited the simd error.

[David Healey]

@Christoph-Hart Apart from the SIMD error everything worked. I did have to enable the execute permission on Projucer - can't remember if I had to do that in the past.

[clevername27]

@David-Healey Does that JUCE commit exist on Remote?

[David Healey]

@clevername27 Not sure what you're asking

[David Healey]

@Christoph-Hart Some issues I've come across:

• The Linux build of Projucer doesn't have execute permission - I think this must be set on a Linux system, not sure.
• The MacOS build of Projucer has not been codesigned/notarized so it gets flagged by gatekeeper
• The export setup Wizard has not been updated so it's still looking in tools/projucer

[Christoph Hart]

The MacOS build of Projucer has not been codesigned/notarized so it gets flagged by gatekeeper

Was the previous build codesigned & notarized?

The export setup Wizard has not been updated so it's still looking in tools/projucer

Good catch!

[dannytaurus]

@Christoph-Hart said in JUCE submodule PSA:

Was the previous build codesigned & notarized?

FWIW I don't think I've ever seen a gatekeeper dialog for Projucer.

[David Healey]

@Christoph-Hart said in JUCE submodule PSA:

Was the previous build codesigned & notarized?

I just checked and no it doesn't seem that it was. I wonder why I never saw a warning.

[David Healey]

@Christoph-Hart The Projucer binary appears to be Apple Silicon only

[JulesV]

@David-Healey Sorry for the noob question,

What we need to do is to download the modules, extras & projucer folders in the submodule repository?

Then copy them to the tools/projucer folder in the latest Hise develop branch that we downloaded them from?

[David Healey]

@JulesV Remove any copies of the HISE source you already have. Then reclone the repo using this command:

git clone --branch develop --recurse-submodules https://github.com/christophhart/HISE.git

That's it, you'll be good to go.

[JulesV]

@David-Healey I am not using GitHub and cloning procedure.

Previously, I was just downloading and compiling the Hise branch. What do I need to do to use it this way?

[David Healey]

@JulesV said in JUCE submodule PSA:

What do I need to do to use it this way?

I don't know, I've never downloaded submodules manually. Google time for you - or just install git and run one command :)

[ustk]

Updated with the new submodule version, selected JUCE 8 (because, yeah, why not...).

During compilation, XCode complains about the Projucer being outdated (v6.1.4)

"This project was last saved using an outdated version of the Projucer! Re-save this project with the latest version to fix this error."

[JulesV]

@David-Healey

I'm leaving the solution here as a note in case others experience this problem. I had to look back to this commit: https://github.com/christophhart/HISE/commit/c948b81f7a86f24a8fce4ea81051c73b7129e2b5

There's a folder named JUCE in the downloaded "Hise-develop" branch. You need to copy all the files from the submodule into this folder.

From now on, the Projucer application will be launched inside this JUCE folder.