VST compile error on Develop Branch (probably a local issue though)
-
Hi,
I'm getting the following error when trying to export a vst on develop branch. I can create standlone fine on develop, and I could also build vst's in the master branch before installing develop. The project I exported here is a new project to remove any possiblity it was something with my main project causing the issue. So this one is literally a sine wave generator and a keyboard to control it with. Still getting the issue:
I've made a video of the export too if it's useful, or maybe the above will suffice and I'm missing something obvious... Any lightbulbs?
Thanks
-
@BM_FORUM Did you extract the VST SDK?
-
@d-healey I had downloaded them when I installed the master branch so I copied them over when I built the develop branch and left the zip sdk alone. The folder looks like this (the vst export worked fine in master):
Could this be causing the issue?
-
@BM_FORUM How many copies of the HISE source do you have on your system?
-
@d-healey Just the one (develop). OK since your first comment, I went and deleted the vst and asio folders and unipped the sdk folder... No idea why, or how it made any difference, but it did! Just compiled successfully. I think I must have missed some updated docs on the sdk setup, I didn't realise they could ship with HISE hence why I discarded the included lot over the separated downloads... all good now, thanks as always!
-
@d-healey Hi, would there be a reason only the VSTix64 compiles my end generally given my SDK folder structure posted above? For some reason x32 doesn't compile. It doesn't end in a fatal error, but rather just.. stops and gives the 'press any key to continue' command. Then nothing is outputted to the folder.
Any help always appreciated
-
@BM_FORUM I see a recent commit that mentions removing a 32bit option, might be related. Who uses 32bit!
- remove 32bit build option (-aXXX defaults to 64bit) 路 christophhart/HISE@1408589
The open source framework for sample based instruments - - remove 32bit build option (-aXXX defaults to 64bit) 路 christophhart/HISE@1408589
GitHub (github.com)
-
@d-healey Ah, that's good enough for me! I didn't think 32bit would be a massively important thing to include in a release, but also see it's included in HISEs auto-generated inno script so wondered if people were generally still packaging it up... Thanks for confirming, I'll just leave 32bit out of it.
-
@BM_FORUM Yeah, I removed almost everything related to 32bit builds in the last days because I think those days are long over. We excluded 32bit from PercX 2 years ago and to this day we haven't received a single request for a 32bit build.
