@d-healey

I think I fixed it, I was on a different version on my MacBook.

@d-healey said in [GUIDE] Complete Setup for Compiling HISE with IPP and FAUST (Windows):

but how will a beginner know if they need it?

Yeah it can be more clearly worded

This is a bit confusing to me, what does it mean?

Again, wording is vague, but for example I had an issue on 4.1.0 where I'd get an wrap::illegal_poly error, which is not present on the develop branch, pretty much what that is trying to say.

I would recommend not calling the folder HISE-develop. Go with the default HISE. That way when you want to switch between branches and commits it's less confusing.

Right, that makes more sense

It's best to use .xml for your main project file.

I didn't know that, good to know.

What does "or project-specific settings" mean? Isn't that the same as File > Settings?

It is, but the settings are project-specific. (I think. AI worded it wrong, I didn't catch that)

I don't see "Export > Export Tools" (is this an AI invention?)

What Christoph said, but I guess it would be clearer for the user to not mention Export Tools

I did make a video about this process recently that you might want to reference - although I assume the default locations for VS, FAUST, and IPP. I also included FFTW as an option.

A video is definitely helpful. I was thinking of adding screenshots but I didn't get to it.

I'll update it now!