# Improvement for multi-format plugin

**URL:** <https://forum.juce.com/t/improvement-for-multi-format-plugin/4843>\
**Category:** Audio Plugins\
**Created:** [February 5, 2010, 10:06am UTC](https://forum.juce.com/t/improvement-for-multi-format-plugin/4843 "2010-02-05T10:06:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![yfede](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/yfede/32/506_2.png) [@yfede](https://forum.juce.com/u/yfede)\
**Post date:** [February 5, 2010, 10:06am UTC](https://forum.juce.com/t/improvement-for-multi-format-plugin/4843/1 "2010-02-05T10:06:57Z")

</div>

I’ve found myself in the need to define what formats of plug-ins to build into the binary depending on the project configuration on Visual Studio.  
I think that surrounding each

#define JucePlugin\_Build\*

with the matching #ifndef is a good idea, so people can override what formats to build by simply defining those macros to whatever their values should be in their project configurations.

I’ve did it myself in my local copy of JucePluginCharacteristics.h, that looks this way now:

[code]#if ! JucePlugin\_Build\_Standalone

// You should turn on these flags to enable the different types of plugin…  
#ifndef JucePlugin\_Build\_VST  
#define JucePlugin\_Build\_VST 1  
#endif

#ifndef JucePlugin\_Build\_RTAS  
#define JucePlugin\_Build\_RTAS 1  
#endif

#ifndef JucePlugin\_Build\_AU  
#define JucePlugin\_Build\_AU 1  
#endif  
#endif  
[/code]

What do you think about this?

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [February 5, 2010, 2:58pm UTC](https://forum.juce.com/t/improvement-for-multi-format-plugin/4843/2 "2010-02-05T14:58:45Z")

</div>

Well, everyone has their own plugin characteristics file anyway, so everyone can mod it as required - but that’s a good idea, I’ll add it to the example code. Thanks!