I'll cleanup all builds tomorrow. The reason I worked on this is that I've trimmed down the system requirements for compiling plugins with HISE - you now don't need VS or Xcode anymore - MS and Apple provide headless compiler tools that can be completely installed with the command line so the installation script that the HISE TUI app runs will be completely hands-off - it basically installs and sets up HISE with Faust & IPP with a single command now.

That's awesome!

Faust & IPP

FFTW please

@Orvillain said in Latest develop won't build in VS2022:

Okie dokie. I'm now at this point:

I would build an older commit. Or is there something you need specifically from the bleeding edge?

Well I've ended up down a rabbit hole for sure! lolololol.

I started off on an older build, and hit the original VS2022 versus VS2026 and our CI build system. So I got the CI devs to add VS2026 support, and started working through issues one by one. I don't necessarily think there is a specific reason for me to be on the bleeding edge. Certainly need to be on a build from sometime in 2026 though. I'll do some more digging later on. Dinner time!

Okie dokie. I'm now at this point:

I would build an older commit. Or is there something you need specifically from the bleeding edge?

@Orvillain ah yes sorry that‘s a different error - I‘m currently in the middle of rewriting the build pipeline on every OS so it‘s expected that something is glitchy - in this case the scriptnode database flag should be zero on dll builds.

Okie dokie. I'm now at this point:

Christoph confirmed our fix — HISE_INCLUDE_SCRIPTNODE_DATABASE=0 in ProjectDllTemplate.cpp is correct. ✅

But there's still a second blocker: the Projucer's VS2026 exporter silently fails to create the VisualStudio2026 output folder. When we rebuild HISE with the template fix, compile_networks will still fail because Projucer can't generate the .sln.

You should tell Christoph:

The HISE_INCLUDE_SCRIPTNODE_DATABASE=0 fix is applied. But there's a second issue: the Projucer in JUCE_customized silently fails when processing the <VS2026> exporter — it creates no Windows output folder at all. The class MSVCProjectExporterVC2026 exists in jucer_ProjectExport_MSVC.h and is registered in jucer_ProjectExporter.cpp, but --resave produces only MacOSX and LinuxMakefile outputs, no VisualStudio2026 folder.

I'm happy to dig in and help debug this, limited as my capabilities are!

hmmmm, oddness aplenty here. I've done that, and I still get this kind of thing:

error C2653: 'zstd': is not a class or namespace name
  node_ids.h(842) — compiling include_hi_tools_03.cpp
  node_ids.h(937) — compiling include_hi_tools_03.cpp  
  node_ids.h(958) — compiling include_hi_tools_03.cpp

error C2065: 'ZDefaultCompressor': undeclared identifier
  node_ids.h(842) — compiling include_hi_dsp_library_01.cpp
  node_ids.h(937) — compiling include_hi_dsp_library_01.cpp
  node_ids.h(958) — compiling include_hi_dsp_library_01.cpp

(same errors repeated across Main.cpp, include_hi_tools_01.cpp)
  

Claude said this:

Not set anywhere in your project. This confirms the DLL project inherits the default HISE_INCLUDE_SCRIPTNODE_DATABASE=1, which pulls in zstd code without the zstd module.

Tell Christoph specifically:

The zstd error is in the DspNetworks DLL project (from compile_networks), not the HISE Standalone. hi_dsp_library.h defaults HISE_INCLUDE_SCRIPTNODE_DATABASE=1, which causes node_ids.h to use zstd::ZDefaultCompressor at lines 842/937/958. But the DLL project template (ProjectDllTemplate.cpp) doesn't include hi_zstd. Either the DLL template needs hi_zstd added, or HISE_INCLUDE_SCRIPTNODE_DATABASE should default to 0 for DLL builds.

The three call sites are in NodeDatabase::ProjectData (line 842), ProjectData::writeProjectData (line 937), and NodeDatabase::Data (line 958).

Either the DLL project template needs hi_zstd added, or HISE_INCLUDE_SCRIPTNODE_DATABASE should be set to 0 for DLL builds, or the zstd:: calls need a guard like #if HISE_INCLUDE_ZSTD.

I already tried deleting the VS solution folder and resaving the Projucer file — same result.

Sorry - wish I could be more thorough, but I don't know anything about this side of HISE!