Cannot open include file: 'ipp.g' on build
-
@blezzbeats You took care of them when you built HISE. Now you have to take care of them for building your project ;)
-
@d-healey Any clue where to start? Lol, the settings above (Use IPP disabled in compiler settings) are correct at least? And I'm sure I don't use the convolution reverb or anything like that. I'm totally lost.
-
Wait wait wait, do I have to compile "plugin" as well is what you're almost saying?
-
@blezzbeats
I think we are talking at cross purposes - which of these versions did you use?
• master
• new_layout
• develop
?
-
@blezzbeats In your project preferences there is a box called Extra Definitions Windows. You need to put USE_IPP=0. And as MikeB said you should be using the develop branch. The master branch is ancient.
-
@MikeB Probably haha, excuse my noobness. I don't know how to get to that view but I downloaded the master ZIP here and presumed I got the latest version. So if I get "new_layout" there I should have it covered?
-
@blezzbeats Click the link that says branches and download the develop branch.
-
@d-healey Thanks for your time man. Now I can't build this one cause of "
Error C1128 number of sections exceeded object file format limit: compile with /bigobj HISE Standalone_App C:\HISE-master 3\HISE-master\projects\standalone\JuceLibraryCode\include_hi_scripting_01.cpp 1"://
-
@blezzbeats said in Cannot open include file: 'ipp.g' on build:
/bigobj HISE Standalone_App C:\HISE-master 3\HISE-
Why does that say
HISE-master 3? -
@d-healey Because it's my third folder of HISE, can that mess it up?
-
@blezzbeats No - it just confuses :-)
-
@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.
-
@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?
-
@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.
-
@blezzbeats or even better - just watch David's video
-
@MikeB Watched in 20 times ;)
-
@blezzbeats Ok - it worked for me the first time.
What's the problem? Leave out ipp.
Describe your steps incl. path -
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.
- Downloaded and installed Visual Studio 2017 and IPP, versions according to the video (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
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:
-
@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 hereSo you built the master branch and then downloaded the develop branch code?
-
Forgot to mention, also added the path to the new build:
