Issue for build on MacOs
-
@ulrik I directly download it from Steinberg, I will delet the other folder, but when I try to unzip the "sdk.zip" it ask me a password for ASIO
-
@Haddock well its NOT 1234 - but if you simply rearrange these then it might be that.
-
Thanks @Lindon !
-
@Haddock how is it going, did you manage to build successfully?
-
@ulrik No sorry I was not here for few days, I relpaced the sdk folder and he gave me the same error, I was wondering if you need to locate the project you want to build in a particular folder or not ? Or the Hise path location enough.
This is my actual sdk folder :
Thanks for your help ! :)
-
@Haddock hmm, looks right to me.
You have to have the right path to Hise but the project you're building is open when you export it to au or vst, so there's no need to set any other path I think -
@ulrik said in Issue for build on MacOs:
You have to have the right path to Hise but the project you're building is open when you export it to au or vst, so there's no need to set any other path I think
Hey ! The VST export still not working with the same "vst2 issue" but the AU export seems to work but I don't find it, not in "App Support / Audio / plugins / etc" and not by searching directly on my computer..
-
@Haddock Have you looked in "yourname/library/audio/plugins/components?
-
@ulrik Yes nothing here.
-
@Haddock said in Issue for build on MacOs:
/Users/macbook/Desktop/HISE/HISE-master/JUCE/modules/juce_audio_plugin_client/VST/juce_VST_Wrapper.cpp:95:10: 'pluginterfaces/vst2.x/aeffect.h' file not found
#include "pluginterfaces/vst2.x/aeffect.h"
^@Haddock
I had this issue and, if I remember correctly, what worked for me was going into the file JUCE_VST_Wrapper.cpp and changing 'pluginterfaces/vst2.x/aeffect.h' to the absolute path. It looks something like this:Macintosh HD/Users/[Your Name]/Downloads/HISE-2.1.0/tools/SDK/VST3 SDK/pluginterfaces/vst2.x/aeffect.h
Hope this helps!
-
@TNTHM said in Issue for build on MacOs:
JUCE_VST_Wrapper.cpp
Thanks for the trick ! I try to do it but it make this error :
/Users/macbook/Desktop/HISE/HISE-master/JUCE/modules/juce_audio_plugin_client/VST/juce_VST_Wrapper.cpp:95:10: 'MACINTOSH SSD/Utilisateurs/macbook/Bureau/HISE/HISE-master/tools/SDK/VST3 SDK/pluginterfaces/vst2.x/aeffect.h' file not found#include "MACINTOSH SSD<U+2069>/<U+2068>Utilisateurs<U+2069>/<U+2068>macbook<U+2069>/<U+2068>Bureau/HISE/HISE-master/tools<U+2069>/SDK<U+2069>/VST3 SDK<U+2069>/pluginterfaces<U+2069>/<U+2068>vst2.x<U+2069>/aeffect.h<U+2069>"
^** BUILD FAILED **
The following build commands failed:
CompileC build/Spacializer_dev.build/Release/Spacializer_dev\ -\ VST.build/Objects-normal/x86_64/include_juce_audio_plugin_client_VST2.o /Users/macbook/Desktop/StrictlyFunStudio/Spacializer/Spacializer_dev/Binaries/JuceLibraryCode/include_juce_audio_plugin_client_VST2.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
Compiling finished. Cleaning up...
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Deleting expired sessions...102 completed.You think I misinform the file?
-
I'm not sure. Changing the path worked for me. Hope someone who knows better can tell you what to try next. Best of luck!
-
@Haddock I think I remember having this issue but not sure of the solution though...
Are you certain to have the path in "Preference/Development/Hise Path" actually set to the HISE folder your using and not an old one? -
@ustk half-a-decade necro but I see this happening when trying to build the most recent develop commit, specifically the plugin version of HISE. Standalone builds fine. Why is it trying to build VST2?
-
@aaronventure unless you have a really good reason - dont bother building the plugin version of HISE...
-
@Lindon I need to run HISE inside PluginDoctor while working on DSP.
Also, I need to be able to thoroughly test and debug MIDI behaviour in a DAW.
-
@aaronventure then I think you will find you are pretty much on your own - sorry.
-
@Lindon so this was super fucking dumb, the vst sdk wasn't properly extracted, it was in the sdk folder which the macOS automatically created when extracting the zip.
Standalone builds fine with it, unlike the Windows version. So when the WIndows version wouldn't build, from the same repo, that gave me a clue.
