Issue compiling HISE on Mac

[dannytaurus]

@d-healey said in Issue compiling HISE on Mac:

@dannytaurus might be ram that is the limiting factor then

Yeah, I thought that too but @bendurso has M2 Mac with 8GB RAM and compiles in 5 mins

[Lindon]

@dannytaurus said in Issue compiling HISE on Mac:

@Christoph-Hart I'm compiling in Xcode, following these instructions:

1. Open HISE/tools/projucer
2. In Projucer, open HISE/projects/standalone/HISE Standalone.jucer
3. Hit the Xcode button at the top
4. In Xcode do Product > Build For > Running

Then wait...

A couple of days ago I tried Product > Run and it launched HISE in less than a minute but now that takes a very long time too, and has crashed the Mac a couple of times.

is step 4 correct? I recall(not on the mac right now) that "Running" isnt the target we use? Dont we use
Build for>Profiling ??

[d.healey]

@Lindon Running = debug build, profiling =release. They're both right, just depends what you want.

[Lindon]

@d-healey said in Issue compiling HISE on Mac:

@Lindon Running = debug build, profiling =release. They're both right, just depends what you want.

and theres me thinking Build for> Test was for debugging....

[d.healey]

@Lindon Why would Apple be that logical :p

[bendurso]

@d-healey Debug is not slower than release? Maybe that's why he takes 30 minutes to compile.

@dannytaurus or are you using Build for profiling?

[d.healey]

@bendurso said in Issue compiling HISE on Mac:

Debug is not slower than release?

Debug will build faster because it doesn't have to optimize as it does for the release.

[bendurso]

@dannytaurus Did you disable x86_64 from "Valid Architectures" on Projucer?

I just was compiling Hise and forgot to remove that option, so it ended up running for about 20 minutes before giving me an faust error. Once I removed the option, it compiled in just 4 minutes. The process uses nearly all the RAM (7GB), but it's still fast.

[dannytaurus]

@bendurso said in Issue compiling HISE on Mac:

@dannytaurus Did you disable x86_64 from "Valid Architectures" on Projucer?

I just was compiling Hise and forgot to remove that option, so it ended up running for about 20 minutes before giving me an faust error. Once I removed the option, it compiled in just 4 minutes. The process uses nearly all the RAM (7GB), but it's still fast.

Thanks for the suggestion.

I think my problem is related to other things running on my MacBook. When I compile is Safe Mode it only takes 13 mins, which is fine by me. I would like to get it down to 4/5 mins but 13 mins is OK.

However, I checked Projucer and the x86_64 was indeed checked - but unchecking it doesn't seem to make any difference here.

In Safe Mode it still took 13 mins to compile and in regular mode I let the build run for 30 mins before I cancelled it.

Since I'm building in Xcode for 'My Mac' (Apple Silicon) I think maybe the x86_64 in the Valid Architectures list doesn't get used.

[dannytaurus]

@d-healey said in Issue compiling HISE on Mac:

@bendurso said in Issue compiling HISE on Mac:

Debug is not slower than release?

Debug will build faster because it doesn't have to optimize as it does for the release.

Compiling a Release build is actually quicker for me than compiling Debug.

In Safe Mode (I can't realistically compile in normal mode):

• Debug takes ~13 mins
• Release takes ~10 mins

The Release app is much smaller too, 44MB compared to 195MB for Debug - is this normal?

EDIT - just tried building Release on GitHub and it was indeed slower - 23 mins compared to 11 mins for Debug.

[d.healey]

@dannytaurus said in Issue compiling HISE on Mac:

44MB compared to 195MB for Debug - is this normal?

Yes, the debug build lacks a lot of optimisations, which makes it larger and should make it faster to build - I think the linking stage is almost completely skipped.