Latest Build Errors
-
Failed Here Too :(
-
@d-healey I re-cloned the repo and scriptnode does compile, but it systematically crashes when opening my project...
I commented all scripts but no luck...
(the project does open with your fork though) -
@ustk Ok I'll try a reclone
-
I'm still getting the same errors
-
@d-healey Mmm... Strange....
-
@d-healey Have you tested on macOS?
-
@ustk No only on GNU/Linux
-
@ustk said in Latest Build Errors:
I re-cloned the repo and scriptnode does compile, but it systematically crashes when opening my project...
There are two options to figure out stuff like that (both are annoying):
- Gradually remove elements from your project to find the culprit module
- Subsequently move back in the Git timeline until you can pinpoint the exact commit that broke it for you. Be aware that sometimes there are intermediate commits which do not compile though.
Let me know if you find the issue / rogue commit, then I'll fix it.
-
@Christoph-Hart Yep I commented out all my scripts but that didn't do it...
And going back in time in the commits behave weirdly as I can't revert the commits back to a certain point (nothing to commit error), but I'll retry ;) -
@Christoph-Hart I have a bunch of errors like this:
../../../../../HISE/hi_snex/snex_core/snex_CallbackCollection.cpp:466:38: error: call of overloaded ‘mov(asmjit::x86::Mem&, juce::int64)’ is ambiguous if (IS_MEM(v)) cc.mov(n, INT_IMM(v));
What's the solution?
-
@Christoph-Hart I managed to resolve the issues by making three casts to (int). Hopefully I didn't break anything, I'll make a pull request.
-
@Christoph-Hart Now I have the latest scriptnode up and running I found a bug. The expansions system seems to be broken, calling functions to get a list of expansions produces an empty array, the list of expansions in the Sample Workspace is empty (pressing refresh does nothing), and clicking the create a new expansion crashes HISE after the prompt is closed. I also noticed that the Projucer settings for
HISE_ENABLE_EXPANSIONS
is no longer there. -
@d-healey I confirm this error. @Christoph-Hart I'd like you to take a look and let me know if you can fix the session preset restore bug while using extensions in the near future :)