The command copy exited?

1

2nd EDIT: This seems to only be an issue when I neglect to initialize my formatReader pointer with nullptr. Now I understand this gets into the territory of undefined behavior but why is there such a strange build error?

EDIT: I found the issue and now I’m more confused.
For some reason including “delete formatReader;” in the destructor stops the program from compiling. I would like to delete the formatReader so I would still appreciate some advise.

I am extremely stuck with this build error. I’m just trying to set up a simple sampler but can’t get my program to compile. Any idea what code changes could cause this kind of error?

The command copy /Y D:\My Data\Programming\JUCE Projects\Just a Sample\Builds\VisualStudio2022\x64\Debug\VST3\Just a Sample.dll D:\My Data\Programming\JUCE Projects\Just a Sample\Builds\VisualStudio2022\x64\Debug\VST3\Just a Sample.vst3\Contents\x86_64-win\Just a Sample.vst3
del /s /q D:\My Data\Programming\JUCE Projects\Just a Sample\Builds\VisualStudio2022\x64\Debug\VST3/Just a Sample.vst3\Contents\moduleinfo.json
if not exist D:\My Data\Programming\JUCE Projects\Just a Sample\Builds\VisualStudio2022\x64\Debug\VST3/Just a Sample.vst3\Contents\Resources\ del /s /q D:\My Data\Programming\JUCE Projects\Just a Sample\Builds\VisualStudio2022\x64\Debug\VST3/Just a Sample.vst3\Contents\Resources && mkdir D:\My Data\Programming\JUCE Projects\Just a Sample\Builds\VisualStudio2022\x64\Debug\VST3/Just a Sample.vst3\Contents\Resources
D:\My Data\Programming\JUCE Projects\Just a Sample\Builds\VisualStudio2022\x64\Debug\VST3 Manifest Helper\juce_vst3_helper.exe -create -version 1.0.0 -path D:\My Data\Programming\JUCE Projects\Just a Sample\Builds\VisualStudio2022\x64\Debug\VST3/Just a Sample.vst3 -output D:\My Data\Programming\JUCE Projects\Just a Sample\Builds\VisualStudio2022\x64\Debug\VST3/Just a Sample.vst3\Contents\Resources\moduleinfo.json
:VCEnd exited with code -1073741819

2

EDIT: reads like you have juce 7.0.6
known issues with the new vst3 moduleinfo.json creator here in other threads on forum

1 Like
3

I’m still having this with 7.0.7 and could not find a solution on the forum. Where should I look?

4

Looking into this I found that the directory path for juce_vst3_helper.exe is wrong. It looks in the plug-in’s build folder while the helper tool has its own build directory. If I edit the command it runs fine in the command shell.

Should be an easy fix. Has this been fixed in the development branch already?

5

Found the culprit.

In jucer_ProjectExport_MSVC.cpp in getExtraPostBuildSteps()

const auto writer = writerTarget->getConfigTargetPath (config) ...

delivers a path that points inside the plugin’s config target path. This however does not work with a custom Binary Location and/or custom Intermediates Path.

A temporary workaround was to patch this and use a hard-wired location, which worked. Someone with better knowledge of the Projucer code should look into this.

1 Like
6

thanks Ans!
I’m sticking with 7.0.5 untill all the bugs around vst3 moduleinfo are cleared up. The bugs in it are shattered here all over the forum, I saw at least 3 different threads about it…