Efficient Debugging in DAW?
-
Hi All,
I am somewhat new to HISE and just came across the first issue where I really need to be running my plugin in debug mode with a DAW as the debug executable. It seems that I can do this by building from the Auto Generated JUCER file and exporting to XCode, but actually building my HISE project takes a LONG time (like 20 minutes or more) because it needs to compile so much stuff.
Does anyone have advice on how to debug for quick changes when testing in a DAW? I want to be able to set breakpoints and write DBG output from the C++ code itself to investigate my custom scriptnode nodes and such.
Thanks!
-
@langermarc19 20 minutes is a long time. Are you sure you're making a debug build? (in XCode it's
Build for Running).Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
Yes, 20 minutes is way too long, especially for Debug builds. My MacBook Air does a full rebuild in Debug mode in something between 1-2 minutes.
-
@d-healey @Christoph-Hart I set the scheme to the Debug build configuration and chose "Debug for Running" and it's still taking a long time.
The HISE version that I used to export the VST/AU initially was the release version. Is that potentially the problem?
-
PS I'm on a 2018 Mac Mini with a 6-core 3GHz Intel i5 and 16GB RAM
-
Was just able to do a rebuild in a little over 5 minutes. Better but not great
-
@langermarc19 My Mac mini 2018 (i7 6 core) takes around 3-4 minutes, however if you're only changing your scriptnode code, it shouldn't do a full rebuild.
Do you include Rubberband? This might increase the build time as it's a complex library.
-
@Christoph-Hart for this one I don't have rubberband included no. But that's good to know I guess, it's not so far out of range if it's taking me ~5 minutes
