# VST SDK v3.6.7 and compiler error when building JUCE plugin

**URL:** <https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282>\
**Category:** Audio Plugins\
**Created:** [March 9, 2017, 9:54pm UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282 "2017-03-09T21:54:46Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![djb-2](https://avatars.discourse-cdn.com/v4/letter/d/73ab20/32.png) [@djb-2](https://forum.juce.com/u/djb-2)\
**Post date:** [March 9, 2017, 9:54pm UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/1 "2017-03-09T21:54:46Z")

</div>

Hi all,

Just a heads up:

Steinberg released a new version of their VST3 SDK.  
Unfortunately they seem to have removed a file that is required by JUCE. MSVC gives the following error:

\modules\juce\_audio\_processors\format\_types\juce\_vst3headers.h(88): fatal error C1083: Cannot open include file: ‘base/source/fatomic.cpp’: No such file or directory (compiling source file …\JuceLibraryCode\juce\_audio\_plugin\_client\_VST3.cpp)

The file fatomic.cpp was present in VST 3 SDK v3.6.6 but seems to be removed in V3.6.7…

---

<div class="post-metadata">

**Author:** ![t0m](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/t0m/32/16413_2.png) [@t0m](https://forum.juce.com/u/t0m)\
**Post date:** [March 10, 2017, 9:47am UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/2 "2017-03-10T09:47:40Z")

</div>

Thank you for reporting.

The new VST3 SDK is almost completely different, and supporting it in JUCE (and getting it properly tested) is too big a job to do before the release of JUCE 5.

One highlight of the new release:

“this maintenance release is mainly a preview version for Linux support”

but I’ve not found any more information about what “preview” means in this context…

---

<div class="post-metadata">

**Author:** ![fbunn](https://avatars.discourse-cdn.com/v4/letter/f/eada6e/32.png) [@fbunn](https://forum.juce.com/u/fbunn)\
**Post date:** [March 12, 2017, 9:38pm UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/3 "2017-03-12T21:38:13Z")

</div>

Is there anywhere to get 3.6.5, then?

---

<div class="post-metadata">

**Author:** ![djb-2](https://avatars.discourse-cdn.com/v4/letter/d/73ab20/32.png) [@djb-2](https://forum.juce.com/u/djb-2)\
**Post date:** [March 12, 2017, 10:02pm UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/4 "2017-03-12T22:02:29Z")

</div>

Hmm the v3.6.6 SDK seems to have been removed from the Steinberg developer page, and only v3.6.7 is available for download (last week when I checked they had both options up, but it seems Steinberg is pushing everyone onto 3.6.7 then?)

---

<div class="post-metadata">

**Author:** ![jonathonracz](https://avatars.discourse-cdn.com/v4/letter/j/da6949/32.png) [@jonathonracz](https://forum.juce.com/u/jonathonracz)\
**Post date:** [March 13, 2017, 12:26am UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/5 "2017-03-13T00:26:11Z")

</div>

JUCE team, if you’re going to go with “not fixing it for now” you should try to work something out with Steinberg to allow redistributing the JUCE-compatible version until you can fix it. Steinberg is not distributing 3.6.6 anymore, and I would host it for others myself but the VST3 license agreement specifically prohibits doing so.

Until then VST building for JUCE is unusable for all new users. **(!!!)** Obviously this is a huge problem and I’m surprised it’s not a top priority.

Also, 3.6.7 (and presumably all future releases) are now available on Github - perhaps it would make sense to include it in the JUCE repo as a submodule in the future? Similar to the CoreAudio SDK integration, it would allow Projucer to get rid of the “VST SDK Path” field in the global settings.

> **[steinbergmedia/vst3sdk](https://github.com/steinbergmedia/vst3sdk)**
>
> vst3sdk - VST 3 Plug-In SDK

EDIT: Checked a prior version of the developer page via wayback machine, Steinberg’s 3.6.6 link is still live. But who knows when they’ll take it down:

[http://www.steinberg.net/sdk\_downloads/vstsdk366\_27\_06\_2016\_build\_61.zip](http://www.steinberg.net/sdk_downloads/vstsdk366_27_06_2016_build_61.zip)

---

<div class="post-metadata">

**Author:** ![djb-2](https://avatars.discourse-cdn.com/v4/letter/d/73ab20/32.png) [@djb-2](https://forum.juce.com/u/djb-2)\
**Post date:** [March 13, 2017, 3:02am UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/6 "2017-03-13T03:02:05Z")

</div>

> [@jonathonracz](#):
>
> Also, 3.6.7 (and presumably all future releases) are now available on Github - perhaps it would make sense to include it in the JUCE repo as a submodule in the future? Similar to the CoreAudio SDK integration, it would allow Projucer to get rid of the “VST SDK Path” field in the global settings.  
> [GitHub - steinbergmedia/vst3sdk: VST 3 Plug-In SDK](https://github.com/steinbergmedia/vst3sdk)

That github repo seems empty though?!? Not impressed by how Steinberg handles this ☹

---

<div class="post-metadata">

**Author:** ![Verbonaut](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/verbonaut/32/11824_2.png) [@Verbonaut](https://forum.juce.com/u/Verbonaut)\
**Post date:** [March 13, 2017, 10:25am UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/7 "2017-03-13T10:25:37Z")

</div>

There is also the SDK v3.6.5 here if anybody needs it [https://sdk.steinberg.net/viewtopic.php?t=211](https://sdk.steinberg.net/viewtopic.php?t=211) but it looks like they’re not keeping many of the old versions online.

---

<div class="post-metadata">

**Author:** ![t0m](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/t0m/32/16413_2.png) [@t0m](https://forum.juce.com/u/t0m)\
**Post date:** [March 13, 2017, 4:18pm UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/8 "2017-03-13T16:18:04Z")

</div>

An update on this: we will shortly be supporting the VST3 SDK V3.6.7 exclusively. You will need to update your SDK when we make the changes.

---

<div class="post-metadata">

**Author:** ![fr810](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/fr810/32/841_2.png) [@fr810](https://forum.juce.com/u/fr810)\
**Post date:** [March 13, 2017, 5:33pm UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/9 "2017-03-13T17:33:19Z")

</div>

OK. It’s on develop now! Linux support will come later.

You will need to rebuild your projucer.

---

<div class="post-metadata">

**Author:** ![ttg](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ttg/32/14456_2.png) [@ttg](https://forum.juce.com/u/ttg)\
**Post date:** [March 14, 2017, 8:40am UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/10 "2017-03-14T08:40:22Z")

</div>

So to make sure I understand: (before updating…)

- Latest develop branch BREAKS older VST3 SDK right?
- New VST3 SDK still capable of building VST2 plug-ins? (since you’ve also removed the VST2 path from projucer).

---

<div class="post-metadata">

**Author:** ![t0m](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/t0m/32/16413_2.png) [@t0m](https://forum.juce.com/u/t0m)\
**Post date:** [March 14, 2017, 8:46am UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/11 "2017-03-14T08:46:30Z")

</div>

- Yes, you must use the latest VST3 SDK on the develop branch tip
- We don’t use any of the VST2 SDK, and haven’t done so for around 4 months - all the VST2 plugin-host interaction is handled by JUCE code

---

<div class="post-metadata">

**Author:** ![fr810](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/fr810/32/841_2.png) [@fr810](https://forum.juce.com/u/fr810)\
**Post date:** [March 14, 2017, 6:05pm UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/12 "2017-03-14T18:05:35Z")

</div>

We just changed the behaviour slightly again: you now need to select the VST3\_SDK folder inside the VST\_SDK folder in the global preferences (or project settings), like this:

 ![](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/7/7e7facb6b2e3c11e80f73e7183514bab35171a68.png)

Sorry for the back&forth on this.

---

<div class="post-metadata">

**Author:** ![jpo](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/jpo/32/503_2.png) [@jpo](https://forum.juce.com/u/jpo)\
**Post date:** [March 17, 2017, 4:43pm UTC](https://forum.juce.com/t/vst-sdk-v3-6-7-and-compiler-error-when-building-juce-plugin/21282/13 "2017-03-17T16:43:36Z")

</div>

In order to get my plugin to build with vstsdk 3.6.7 and the “-stdlib=libstdc++” flag for clang, I had to replace

`Update::DeferedChangeListIterConst it =`

in VST3\_SDK/base/source/updatehandler.cpp line 110 with:

`Update::DeferedChangeList::iterator it =`
