"HISE path not set" error in Win batch compile script

[gorangrooves]

@d-healey Correct. Nothing gets output there.

[d.healey]

@gorangrooves What happens if you comment out the VST3 compile, does it build the standalone then?

[gorangrooves]

@d-healey It doesn't compile.

HISE source is C:\HISE-develop
HISE path is C:\HISE-develop\projects\standalone\Builds\VisualStudio2022\x64\Release\App\HISE.exe
HISE SDK path set to C:\HISE-develop
ERROR: `"I:\AUDIO TEMPORARY\HISE PROJECTS\Handy Drums- Flamenco Percussion"` is not a valid path
Exporting "Handy Drums- Flamenco Percussion" Standalone

==============================================================================
EXPORT ERROR: Preset file not found
==============================================================================

Re-saving file: I:\AUDIO TEMPORARY\HISE PROJECTS\Handy Drums- Flamenco Percussion\Binaries\AutogeneratedProject.jucer
Finished saving: Visual Studio 2022
Finished saving: Xcode (macOS)
Finished saving: Xcode (iOS)
Finished saving: Linux Makefile
Compiling 64bit Instrument plugin Handy Drums- Flamenco Percussion ...
MSBuild version 17.8.3+195e7f5a3 for .NET Framework

  Handy Drums- Flamenco Percussion_SharedCode.vcxproj -> I:\AUDIO TEMPORARY\HISE PROJECTS\Handy Drums- Flamenco Percuss
  ion\Binaries\Compiled\Shared Code\Handy Drums- Flamenco Percussion.lib
  Handy Drums- Flamenco Percussion_VST3.vcxproj -> I:\AUDIO TEMPORARY\HISE PROJECTS\Handy Drums- Flamenco Percussion\Bi
  naries\Compiled\VST3\Handy Drums- Flamenco Percussion.vst3
Press any key to continue . . .

[gorangrooves]

@gorangrooves Perhaps it is using outdated AutogeneratedProject and batchCompile, as it didn't rebuild those.
I have to specify the path without "" to build those resources, then enclose the path in "" to compile the instrument.
Let me re-run both of those.

[gorangrooves]

@d-healey Removing the code to generate the vst3, managed to compile the standalone app.

Unfortunately, this process is worse than manual

@Christoph-Hart Am I correct to conclude that compiling using CI mode does not handle any spaces in the path folder names and perhaps in the project name?

I'll have to rename my folders to exclude spaces to see if that does the trick.

[d.healey]

@gorangrooves said in "HISE path not set" error in Win batch compile script:

Am I correct to conclude that compiling using CI mode does not handle any spaces in the path folder names and perhaps in the project name?

The commandline won't work with spaces unless they are quoted or escaped.

[Christoph Hart]

Yeah I‘m also always messing up the paths with whitespaces in my scripts. The good news is that once you‘ve got the script working it‘s a breeze until you come back to it a few months later and something broke :)

[gorangrooves]

@Christoph-Hart I hope that I can get away with just making the folder paths without white space.
Changing project XML will require me to change the main container in the project, which will require me to change all references to it. Compiled plugins would also be affected, as will all my installer projects.

@d-healey As I demonstrated above, quotes won't work, as part of the script works with them, then the other part works without them. It is impossible to run the script completely with or without the quotes if there are white spaces in the folder path. (I hope it is only the folder path white spaces....)

[d.healey]

@gorangrooves said in "HISE path not set" error in Win batch compile script:

hope that I can get away with just making the folder paths without white space.

Did you try escaping the spaces?

[gorangrooves]

@d-healey let me try

[gorangrooves]

@d-healey No, that doesn't work either. The CMD uses ^ to escape, but is not being read by anything else, so that didn't work.
What can of worms did I open?...

[d.healey]

@gorangrooves Can you send me the project?

[gorangrooves]

@d-healey Yes. I'll pack it up and dm you.

[d.healey]

@gorangrooves Ok, I'll take a look tomorrow

[gorangrooves]

@d-healey Alright. Removing white spaces from the folder paths fixed the issues. I left the project name unchanged. The app compiled with only the app compiling directive in the script. I will re-introduce the VST3 portion of the script and see if it all works as it should.

[gorangrooves]

@d-healey YES! That worked. Now to add regular vst and AAX.

[d.healey]

@gorangrooves Excellent, no need for me to do anything then :)

[gorangrooves]

@d-healey Success. Managed to compile AAX and VST2 just as well. Thank you, Dave, and thank you, Christoph!