Installing Samples Dialog....
-
@d-healey yep
-
-
Does it export if you point it to your usual source code?
-
@d-healey yes
Filos-MacBook-Pro:~ filo$ /Users/filo/Filo/VST\ Project/TEster/Binaries/batchCompileOSX ; exit; Re-saving file: /Users/filo/Filo/VST Project/TEster/Binaries/AutogeneratedProject.jucer Finished saving: Visual Studio 2017 - Builds/VisualStudio2017/ Finished saving: Xcode (MacOSX) Finished saving: Linux Makefile Compiling Standalone application Tester ... ▸ Building Tester/Tester - App [Release] ▸ Check Dependencies ▸ Compiling PresetData.cpp ▸ Compiling CopyProtection.cpp ▸ Compiling include_hi_components.cpp
-
Weird, you found a new issue :p Let us know if the app asks about installing/locating samples :)
-
@d-healey i.e. I cannot compile if a source code is in Download or trash folder. I guess it's a permission issue. But just a guess
-
-
I cannot compile if a source code is in Download or trash folder. I guess it's a permission issue. But just a guess
That could be it. I remember I had a similar issue with trying to compile on my shared drive, I had to put it on the MacOS desktop.
So that screen shot is what should show with Christoph's original code. Can you try again with my code but move it to another location to try to avoid the issue you had before? You can do a debug build to make it faster.
-
@d-healey Figured it out. Permission denied on Projucer.app (the one in you source code). Will try to replace it
/HISE-develop-davo/tools/Projucer/Projucer.app/Contents/MacOS/Projucer: Permission denied
-
@hisefilo Compiling :) on MacOS, no app will be executed unless it's signed/notarised or compiled locally
That gives the permission rejection -
@hisefilo That makes sense, you can swap out the Projucer app for the one that works on your system then :)
-
@d-healey yes, already compiling that way.
-
@d-healey still asking for samples.
!
-
@hisefilo Yeah but did it ask you to locate or install?
-
-
@hisefilo Thanks, you get the same result as me.
Now we have to figure out why Lindon is getting a different result...
-
Not sure if it's related, but I had to disable both in the Projucer project.
Then on my instrument project I add extra definitions to hide the buttons.
entering this only shows the "locate" button:HISE_SAMPLE_DIALOG_SHOW_INSTALL_BUTTON=0
and entering this only shows the "install" button:
HISE_SAMPLE_DIALOG_SHOW_LOCATE_BUTTON=0
-
@dustbro Is this using my develop branch of HISE? I didn't have to touch those properties in hi_core when I exported, they were both set as default.
-
@d-healey said in Installing Samples Dialog....:
Is this using my develop branch of HISE?
no. this is the scriptnode branch
-
@dustbro That doesn't contain my fix so won't help Lindon here :p