The JUCE cross-platform C++ framework, with DISTRHO/KXStudio specific changes
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

54 lines
2.2KB

  1. /*
  2. ==============================================================================
  3. This file is part of the JUCE library.
  4. Copyright (c) 2013 - Raw Material Software Ltd.
  5. Permission is granted to use this software under the terms of either:
  6. a) the GPL v2 (or any later version)
  7. b) the Affero GPL v3
  8. Details of these licenses can be found at: www.gnu.org/licenses
  9. JUCE is distributed in the hope that it will be useful, but WITHOUT ANY
  10. WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
  11. A PARTICULAR PURPOSE. See the GNU General Public License for more details.
  12. ------------------------------------------------------------------------------
  13. To release a closed-source product which uses JUCE, commercial licenses are
  14. available: visit www.juce.com for more information.
  15. ==============================================================================
  16. */
  17. // Your project must contain an AppConfig.h file with your project-specific settings in it,
  18. // and your header search path must make it accessible to the module's files.
  19. #include "AppConfig.h"
  20. #include "../utility/juce_CheckSettingMacros.h"
  21. #if JucePlugin_Build_RTAS
  22. #include "juce_RTAS_DigiCode_Header.h"
  23. /*
  24. This file is used to include and build the required digidesign CPP files without your project
  25. needing to reference the files directly. Because these files will be found via your include path,
  26. this means that the project doesn't have to change to cope with people's SDKs being in different
  27. locations.
  28. Important note on Windows: In your project settings for the three juce_RTAS_DigiCode.cpp files and
  29. the juce_RTAS_Wrapper.cpp file, you need to set the calling convention to "__stdcall".
  30. If you don't do this, you'll get some unresolved externals and will spend a long time wondering what's
  31. going on... All the other files in your project can be set to use the normal __cdecl convention.
  32. If you get an error building the includes statements below, check your paths - there's a full
  33. list of the necessary Digidesign paths in juce_RTAS_Wrapper.cpp
  34. */
  35. #include <CEffectProcessMIDI.cpp>
  36. #include <PlugInUtils.cpp>
  37. #endif