Moonbase
-
@tobbentm Now that HISE works with JUCE 6 and 8, this might be relevant. It’s not something I’m interested in right now, but maybe others will be :)
-
@bendurso Yeah, I saw some threads about JUCE 8 in HISE!
Is it fully supported already?
Caught me a bit by surprise, thought the JUCE license would prohibit that, but happy to see this.I know we've had a number of HISE users create accounts lately, but I'm not sure who is live yet.
-
@tobbentm so if we build hise with juce 8, we can use the moonbase module for activations?
-
@jeffd Our JUCE module is compatible with JUCE 8 out-of-the-box, so while I don't know the exact steps necessary to include it in a HISE project, in principle it should work, yes!
-
I bet if i try it it will probably break my project lol. no idea about any of this honestly.
I was assuming HISE only worked with juce6.
"The JUCE code is now handled as a git submodule so you can switch versions." --anyone know if that is an accurate statement?
-
@jeffd yup recompiled HISE yesterday without any issues so far. The setup is a bit different now however
-
do you have to change something here:
git clone --branch develop --recurse-submodules https://github.com/christophhart/HISE.git
how do i point to juce 8?
or this more complicated than that perhaps?
-
@jeffd The JUCE submodule is its own git repo with 2 branches juce6 and juce8. Go into that folder and checkout juce8
I think you'll also need a JUCE8 licence, not sure.
-
@David-Healey im on an old build before christoph switched to the submodules.
so im not sure if i should do that first ?
-
@jeffd Definitely. You can't use JUCE 8 without the submodule update.
-
@dannytaurus so i got hise to build with juce 8, but ive missed a step i think. when trying to export a plugin and build an audio unit i get this error:
Desktop/HISE/JUCE/modules/juce_core/system/juce_TargetPlatform.h:177:8: "Building for OSX 10.10 and earlier is no longer supported!"
177 | #error "Building for OSX 10.10 and earlier is no longer supported!"im looking in the projucer and it says it set for macos deployment target of 11.0
anyone run into this error?
what is Building for OSX 10.10 coming from?
-
@jeffd I can't imagine JUCE 8 would build on an OS as old as OS X 10.10.
JUCE 8 was 2023 and OS X 10.10 was 2014.
EDIT: just saw you mentioned 11.0, so not sure what's happening there, sorry.
-
@dannytaurus yeah ive been bangin my head trying to figure out whats going on.
it keeps reverting back to 10.9 when i try to export a plugin, yet ive selected the macos deployment target of 11.0 in the projucer.
-
-
@David-Healey yeah i believe so.
i tried it a million times, but maybe im missing something
-
so i had to create a patch on the batchfile to get it to stop reverting to 10.9.
I never would have figured that out on my own, I used cursor. And im wondering if somehow i compiled hise wrong going from 6 to 8?
And now Ive changed the macos deployment target to 10.13. in projucer. So ill make another test plugin and see if it works at some point.
Still just puzzled why it kept doing that.
-
-
every time i tried to compile a binary from HISE, i got an error saying that building for OSX 10.10 and earlier was no longer supported.
so I patched this code:
Force macOS deployment target for JUCE 8 (export keeps generating 10.9)
PBXPROJ="Builds/MacOSX/Baikonur 4.xcodeproj/project.pbxproj"
if [ -f "$PBXPROJ" ]; then
echo "Patching MACOSX_DEPLOYMENT_TARGET to 10.13 for JUCE 8..."
sed -i '' 's/MACOSX_DEPLOYMENT_TARGET = 10.9;/MACOSX_DEPLOYMENT_TARGET = 10.13;/g' "$PBXPROJ"
sed -i '' 's/MACOSX_DEPLOYMENT_TARGET = 10.10;/MACOSX_DEPLOYMENT_TARGET = 10.13;/g' "$PBXPROJ"
fion the batchfile to get it to stop reverting to 10.9
NOT my code or idea..was from an LLM.
-
every time i tried to compile a binary from HISE, i got an error saying that building for OSX 10.10 and earlier was no longer supported.
When you "export" from HISE, HISE creates a JUCE project with an autogenerated juicer file. If you open that in Projucer you can change the macOS target, click save and open in IDE and compile it - if you then reexport from HISE the juicer file will be recreated and your changes overwritten, that's probably the issue you were running into.
Probably a good idea to open a github issue on the JUCE submodule to let Christoph know about this problem when using JUCE 8.
-
@David-Healey said in Moonbase:
if you then reexport from HISE the juicer file will be recreated and your changes overwritten, that's probably the issue you were running into
yes i believe this was the issue.
but im also wondering if i somehow screwed up changing over from 6 to 8. -
H HISEnberg referenced this topic
