CLANG errors on Plugin export
-
Morning all
For the first time in a few projects I've an error on the mac side of compiling a vst instrument and wondered if anyone had any info/pointers as to what is the issue:
[ARCHIVE 0 - Shared Code] Compiling PresetData.cpp
clang: error: unable to execute command: Killed: 9
clang: error: clang frontend command failed due to signal (use -v to see invocation)I'm on a silicon mac Sequoia15.7.4 running the latest commit xcode 16.4
Windows side absolutely nice issue when compiling the vst
-
@JamesC Try an older version of xcode
-
@David-Healey Thanks will try that next
-
@David-Healey SO rolled back as far as I can on this machine same errors. Its odd as other plugins exporting fine.
This one relies on audio loop players and embedded audio files is this another possible cause of the issue?
Thanks
-
@JamesC said in CLANG errors on Plugin export:
This one relies on audio loop players and embedded audio files is this another possible cause of the issue?
Could be. Make a minimal test project and gradually add the elements you think might be causing the issue. Clean the build folder between each recompile.
-
@David-Healey Odd so I started doing that and each time nothing worked. Then I switched to removing audio files out of the folder. If I go over 20 audio files to embed thats whats causes the clang error.
So I wonder what the work arounds are to having large amounts of embedded audio files, in this current project there are 154 audio files that are used in this plugin.
-
@JamesC 50mb is about the limit https://docs.hise.dev/working-with-hise/settings/project.html#embed-audio-files
-
@David-Healey ah ok so essentially revert to having a sampler instead, or audio wave form and let users load in the audio or their own audio also?
If that second option is the case, using a preset browser can users save the presets witht he adio they've uploaded priiding the fodler is kept consistent?
-
@JamesC You can include as many audio files as you need, but instead of embedding them you need to provide them as an AudioResource.dat file that you place into the app data folder.
@JamesC said in CLANG errors on Plugin export:
using a preset browser can users save the presets witht he adio they've uploaded priiding the fodler is kept consistent?
The built in preset system stores/restores the state of components on the interface that have saveInPreset enabled. So if you have a component with a reference to the audio file (a waveform for example) then it should be saved with the preset.
-
@David-Healey SO jsut so I can check I've got this right...
Go into export and export pooled files to binary resource.
Then at this point do I delete the audio files int the audio files folder and replace with the .dat before I compile? or leave everything where it is?
-
@JamesC Never delete your original audio files. Carry on in HISE as if nothing has changed, but when it comes time to compile and deliver your plugin, uncheck embed audio files, and have your installer place the .dat file in the app data folder.
-
@David-Healey Ah yes ok this makes sense thanks so much
