Export Help PLEASE ._.

[MattiesMusic]

I'm just lost, I have not even the slightest idea anymore.
it is has been like this every time I want to export.
I've tried everything; With IPP, without IPP, build through projucer, ... I've even reinstalled HISE a few time...

(Trying to export VSTi 32bit/64bit)

I'm getting about 30-100 warnings a second and only 2 error lines:

c:\program files\hise\hi_scripting\scripting\scriptnode\api\dspnetwork.cpp(68): error C2653: 'stk': is not a class or namespace name (compiling source file ..\..\JuceLibraryCode\include_hi_scripting_03.cpp) [C:\Users\matth\Desktop\HISE-SampleFolder\FreeFlute\Binaries\Bu
ilds\VisualStudio2017\FreeFlute_SharedCode.vcxproj]
c:\program files\hise\hi_scripting\scripting\scriptnode\api\dspnetwork.cpp(68): error C2061: syntax error: identifier 'StkFactory' (compiling source file ..\..\JuceLibraryCode\include_hi_scripting_03.cpp) [C:\Users\matth\Desktop\HISE-SampleFolder\FreeFlute\Binaries\Buil
ds\VisualStudio2017\FreeFlute_SharedCode.vcxproj]

[MattiesMusic]

if I try to build in VS 2017 I get the same errors, except for 1 more:

Severity	Code	Description	Project	File	Line	Suppression State
Error	LNK1104	cannot open file 'FreeFlute_Debug x86.lib'	FreeFlute_VST	C:\Users\matth\Desktop\HISE-SampleFolder\FreeFlute\Binaries\Builds\VisualStudio2017\LINK	1	

[d.healey]

Don't build 32bit

[MattiesMusic]

Hi, thx for the fast reply.

unfortunately, I have the exact same issue when trying to build 64bit

[d.healey]

@MattiesMusic clean the build folder before rebuilding

[MattiesMusic]

still the same errors...

[MattiesMusic]

@d-healey
I have taken notice I accidentally buildt in debug mode, I have tried in Release x64 now too, and still the same errors.
even after cleaning the build folder like you said

In addition to the 3 errors I'm getting a total of 519 warnings
(a lot less than the 999+ it was showing first)

[d.healey]

Which version of HISE are you using?

[MattiesMusic]

@d-healey
Srry for late response.
I'm using version 2.0.0

[d.healey]

@MattiesMusic That version's ancient and shouldn't be used for production. You need to build HISE from source, either using the Master or Develop branch.

[MattiesMusic]

@d-healey
unfortunately, I have already tried that, but with no success.
I followed through step by step doing exactly everything the way it was done in the tutorial, but VS 2017 blasted out errors like a machine gun.
even without IPP enabled.

That's why I had to go with the installer, since nothing else worked.

[d.healey]

@MattiesMusic That's the problem, if you can't compile HISE then you can't compile plugins, the both processes are the same. So get HISE compilation working first. We can do a screen share session if you want.

[MattiesMusic]

@d-healey
I'll wipe every single trace of HISE from my computer and try one more time to build it.
But if it doesn't work again, a screen share session would be appreciated.

I'll reply to this when it has either worked or it hasn't.

Tho a big thank you for the support so far, I really appreciate that.

[MattiesMusic]

It worked; I was able to build HISE! :D
I don't know if this has anything to do with it, but the only thing I did differently this time, was in GitHub, instead of just clicking "download zip", I went to releases and downloaded the .zip there.

I've just now also made a test plugin with some sample & 1 button to test if everything works,
and it works! :]
I'm so chuffed to bits that it's all working now!
I can now finally make free plugins for my community :D

A REALLY BIG thanks for the support!

[d.healey]

@MattiesMusic said in Export Help PLEASE ._.:

I went to releases and downloaded the .zip there.

I'm glad it worked but you're still using an ancient version of HISE, so don't make any bug reports :p

[MattiesMusic]

@d-healey
I did build the latest version I could find under "releases" .-.

[d.healey]

@MattiesMusic Yes but look at the date, it's from 2019. The latest release is not the latest version. The Develop branch is the latest version but Master branch might be a little more stable (although I haven't had any issues with the Develop branch).

[MikeB]

@MattiesMusic did you use one of these two versions?

[MattiesMusic]

@d-healey
oh, makes sense