Trying to compile the develop branch....

[Lindon]

@d-healey said in Trying to compile the develop branch....:

Why do this? Everything should be setup correctly by default.

Because Projucer said my default paths were wrong...

so I reset the paths back to the "defaults"

C:\JUCE etc.

ran the compile again -- same error set.

Projucer is complaining (or telling me) theres a more up to date version of JUCE to downlaod - should I do that? - I'm pretty sure the One I have is very old...

[d.healey]

@lindon Are the HISE module paths correct? Mine are set to ../../

[d.healey]

@lindon said in Trying to compile the develop branch....:

I'm pretty sure the One I have is very old

6.1.3 is included with the develop branch

[Lindon]

@d-healey said in Trying to compile the develop branch....:

@lindon Are the HISE module paths correct? Mine are set to ../../

"HISE module paths"??? Where are they ?

[d.healey]

@lindon

[Lindon]

@d-healey - oh yes - silly me...

yep they are set to: ../../

[Lindon]

@d-healey

So all of the HISE paths seem correct but the JUCE ones tell me this:

but as soon as a reset the global path to
:C\HISE\JUCE\modules

these resolve..

[Lindon]

Ok so I deleted HISE from my system (a slightly unsettling moment) and reinstalled from the latest develop commit.

I ignored Projucers complaints about the HISE path not being set, and there being a newer version of JUCE to install.

Now Projucer is no longer complaining about failing to find the JUCE modules - so that's progress.

But... when I compile I get the same errors I did at the start, which all look like errors in the HISE source code - but that cant be correct can it? It seems VS2017 is finding all the files it needs to find but doesnt like the contents of
snex_indextypes.h

• perhaps there is a more reliable earlier commit I could use? Can someone point me at such a beast?

[d.healey]

@lindon Maybe the version of Projucer is wrong (I haven't tested on Windows yet). What version do you get with the develop branch?

[Lindon]

@d-healey said in Trying to compile the develop branch....:

@lindon Maybe the version of Projucer is wrong (I haven't tested on Windows yet). What version do you get with the develop branch?

I see this when I ask:

[Lindon]

Well I'm not getting any further with this...

Can anyone confirm they have built the latest develop branch on windows?

[Matt_SF]

@lindon Confirmed : Latest commit of dec. 22 builds just fine. Until you solve the issue, I can send you the built version if you want to try it...

[Lindon]

@matt_sf thanks for the offer but i have a fairly high tempo build cycle for the plugins so having a HISE that works but where I cant build my own products inst really much help to me...

sigh, OK well maybe its the zip thats not correct - let me go try the git based install - is there a helpful @d-healey video covering this specifically I wonder...

edit; oh there it is:... https://www.patreon.com/posts/git-version-59469186

[Lindon]

...sadly no, its not the zip. So I git cloned HISE and branch(ed) to develop and unpacked the SDKs and ran a compile(ignoring projucers complaints).

I get the same output - syntax problems in snex_indextypes.h

1>c:\hise\hi_dsp_library\snex_basics\snex_indextypes.h(64): error C2825: 'IndexType': must be a class or namespace when followed by '::' (compiling source file ....\JuceLibraryCode\include_hi_dsp_library_01.cpp)

Can someone point me at a recent commit that reliably works on Windows?

[d.healey]

@lindon I'll test develop branch on my Windows system in an hour and let you know what I find out.

[Lindon]

@d-healey said in Trying to compile the develop branch....:

@lindon I'll test develop branch on my Windows system in an hour and let you know what I find out.

thanks mate..

[d.healey]

@lindon It compiled for me without issue. I downloaded the latest develop (via zip file). The only change I made was to disable IPP. Also I'm using Visual Studio 2019 but that shouldn't make any difference.

[Matt_SF]

@lindon Also, HISE is compiling here on VS17 with IPP

[Lindon]

Well I'm at a complete loss what to do now....

@Christoph-Hart - any ideas?

[Lindon]

this is what the Visual Studio 2017 page looks like in Projucer:

does that look OK?