Cannot open include file: 'ipp.g' on build

[MikeB]

@blezzbeats No - it just confuses :-)

[d.healey]

@blezzbeats Rule number 1, never have more than 1 copy of the HISE source code on your system - unless you know exactly what you're doing.

[blezzbeats]

@d-healey So my project is on another hard drive, but I'm opening it with the build on C:, can this have anything to do with it? Should I move the folders over or something?

[d.healey]

@blezzbeats Shouldn't make a difference. Delete every copy of the source code you have. Download the develop branch. Point your project (in the project's preferences) to the location that you have downloaded the develop branch to.

[MikeB]

@blezzbeats or even better - just watch David's video

[blezzbeats]

@MikeB Watched in 20 times ;)

[MikeB]

@blezzbeats Ok - it worked for me the first time.
What's the problem? Leave out ipp.
Describe your steps incl. path

[blezzbeats]

@MikeB

Well, right now I've managed to build the latest release (I think) after your previous much appreciated help. Trying again to compile VST of my project, not very successful at all.

1. Downloaded and installed Visual Studio 2017 and IPP, versions according to the video (successfully built the master branch but not the latest build)
2. Deleted all the old stuff, downloaded develop branch and extracted SDKs in the SDK folder from here
   
   This is the path
   

Disabled IPP in these places:

Saved and opened in VS2017, successfully built release.

Opened new build, opened my project from HISE standalone (the new build), path:

Version and settings after loading project>

Everything seems to work on the interface preview.

Attempting to compile VST
Tried 64bit and 32bit separately and 64/32 bit. Getting red fails all over the place. Getting this wonderful wall of wonder:

[d.healey]

@blezzbeats said in Cannot open include file: 'ipp.g' on build:

successfully built the master branch but not the latest build)
Deleted all the old stuff, downloaded develop branch and extracted SDKs in the SDK folder from here

So you built the master branch and then downloaded the develop branch code?

[blezzbeats]

Forgot to mention, also added the path to the new build:

[blezzbeats]

@d-healey Yes but I deleted the master branch before downloading the develop branch and building that instead

[d.healey]

@blezzbeats

Yes but I deleted the master branch before downloading the develop branch and building that instead

Well that won't work. You can't build your plugin using a different version of the source.

Also your path is set to HISE-master...

Delete every copy of the source, download the develop branch, build the develop branch, point your project to the develop branch, and try building your project.

[blezzbeats]

@d-healey Sorry but I don't understand at all. I deleted every copy of the source before building the "release" branch, when I download that zip it's called HISE-master.zip. So C:/HISE-master is where i point my project to. Or is pointing my project not the same as setting the path?

[blezzbeats]

@blezzbeats Develop branch I mean, thats where I downloaded the source code. Not release.

[MikeB]

@d-healey Strangely, all the branches are the same.
Is there a bug with Git?
All three branches I downloaded are called Master and have the same content from 28.08.21.

If that's true, the good man can compile himself silly, of course.

[blezzbeats]

I thought it was suspiciously similar lol, got Git and will try that

[d.healey]

Interesting, they are all downloading as master. I use git so I never notice, smells like a bug to me.

[MikeB]

@d-healey is probably one

[d.healey]

@blezzbeats Looks like you're building the master branch for now then

[blezzbeats]

@MikeB @d-healey Git did the trick, feeling like a proper hacker now :grinning_face_with_smiling_eyes: Now to see how it handles my old old wooden project