Exporting as VSTi

[qarsa]

Hello guys!
The fact is that I decided to export my plug-in to VSTI but during compilation in the command line I'm getting this message.

Re-saving file: C:\Users\qarsa\Music\Brighter\Binaries\AutogeneratedProject.jucer
Finished saving: Visual Studio 2017
Finished saving: Xcode (MacOSX)
Finished saving: Xcode (iOS)
Finished saving: Linux Makefile
Compiling 64bit Instrument plugin Brighter ...
Microsoft (R) Build Engine версии 15.9.21+g9802d43bc3 для .NET Framework
(C) Корпорация Майкрософт (Microsoft Corporation). Все права защищены.

C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Current.targets(108,3): error MSB4019: импортированный проект "C:\Program Files (x86)\Microsoft VisualStudio\2017\Community\Common7\IDE\VC\VCTargets\Platforms\x64\Platform.targets" не обнаружен. Проверьте правильность пути в объявлении <Import> и убедитесь в наличии файла на диске. [C:\Users\qarsa\Music\Brighter\Binaries\Builds\VisualStudio2017\Brighter_SharedCode.vcxproj]
Для продолжения нажмите любую клавишу . . .

The same problem with a Standalone export.

How can i fix that? Please help

[d.healey]

I think some important parts of the error message might be in the Cyrillic which I can't read.

[Christoph Hart]

@d-healey said in Exporting as VSTi:

some important parts

Actually EVERY important part :)

[qarsa]

@Christoph-Hart Here's the translation)

Re-saving file: C:\Users\qarsa\Music\Brighter\Binaries\AutogeneratedProject.jucer
Finished saving: Visual Studio 2017
Finished saving: Xcode (MacOSX)
Finished saving: Xcode (iOS)
Finished saving: Linux Makefile
Compiling 64bit Instrument plugin Brighter ...
Microsoft (R) Build Engine version 15.9.21+g9802d43bc3 for .NET Framework
(C) Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Current.targets(108,3): error MSB4019: imported project "C:\Program Files (x86)\Microsoft VisualStudio\2017\Community\Common7\IDE\VC\VCTargets\Platforms\x64\Platform.targets" not found. Verify that the path in the <Import> declaration is correct and that the file is on disk. [C:\Users\qarsa\Music\Brighter\Binaries\Builds\VisualStudio2017\Brighter_SharedCode.vcxproj]
Press any key to continue . . .

[AxiomCrux]

@qarsa did you ever happen to figure this out? I am also encountering this

[d.healey]

@AxiomCrux have you compiled HISE?

[AxiomCrux]

@d-healey No, I was trying to use the built-in export feature, does that require me to compile HISE?

I tried searching for a tutorial or some information about using the built-in compiler script to figure out how to get a plug-in beta test installer for Mac and PC. I believe I found a video you had made for the process on Mac, but I couldn't find anything for Windows.

I was able to get a Mac VST compiled that works, but on PC I've not yet, as I couldn't find anything on the forum or your YouTube to help me troubleshoot, and the error I am currently getting makes it seem like the compiler script isn't generating a Visual Studio project

[d.healey]

@AxiomCrux said in Exporting as VSTi:

No, I was trying to use the built-in export feature, does that require me to compile HISE?

When you "export" from HISE what actually happens is HISE builds a JUCE project for your plugin and runs the compiler to build it. This is the same process as compiling HISE itself.

Also you generally want to be compiling your projects using the same version as the source code that was used to build HISE, otherwise you might end up with weird conflicts.

So generally the first step is to compile HISE. That way you know everything is setup correctly for compiling. Then you export your project.

@AxiomCrux said in Exporting as VSTi:

built-in compiler script to figure out how to get a plug-in beta test installer for Mac and PC. I believe I found a video you had made for the process on Mac

I would advise in general not to run scripts (even from me) unless you understand what the script is doing. Scripts can do a lot of damage if not setup and used correctly.

All my build script does is the same manual steps you'll do when exporting your project from HISE. So start with the manual version, then you'll be able to follow along with what the script is doing.