poweraudio / JUCE

Fork of JUCE with fixes for ppc64le

PowerAudio fork of JUCE

This fork of JUCE has the following changes:

• Fixed linker errors on IBM Power related to undefined symbols in libpng (see JUCE#1339).
• Added a fallback implementation of SIMDRegister for platforms that don’t have native SIMD support (see JUCE#1342).
• Fixed VST 3 plugin generation on Power (see JUCE#1344).

---

JUCE is an open-source cross-platform C++ application framework for creating desktop and mobile applications, including VST, VST3, AU, AUv3, AAX and LV2 audio plug-ins and plug-in hosts. JUCE can be easily integrated with existing projects via CMake, or can be used as a project generation tool via the Projucer, which supports exporting projects for Xcode (macOS and iOS), Visual Studio, Android Studio, and Linux Makefiles as well as containing a source code editor.

Getting Started

The JUCE repository contains a master and develop branch. The develop branch contains the latest bug fixes and features and is periodically merged into the master branch in stable tagged releases (the latest release containing pre-built binaries can be also downloaded from the JUCE website).

JUCE projects can be managed with either the Projucer (JUCE's own project-configuration tool) or with CMake.

The Projucer

The repository doesn't contain a pre-built Projucer so you will need to build it for your platform - Xcode, Visual Studio and Linux Makefile projects are located in extras/Projucer/Builds (the minimum system requirements are listed in the minimum system requirements section below). The Projucer can then be used to create new JUCE projects, view tutorials and run examples. It is also possible to include the JUCE modules source code in an existing project directly, or build them into a static or dynamic library which can be linked into a project.

For further help getting started, please refer to the JUCE documentation and tutorials.

CMake

Version 3.22 or higher is required. To use CMake, you will need to install it, either from your system package manager or from the official download page. For comprehensive documentation on JUCE's CMake API, see the JUCE CMake documentation. For examples which may be useful as starting points for new CMake projects, see the CMake examples directory.

Building Examples

To use CMake to build the examples and extras bundled with JUCE, simply clone JUCE and then run the following commands, replacing "DemoRunner" with the name of the target you wish to build.

cd /path/to/JUCE
cmake . -B cmake-build -DJUCE_BUILD_EXAMPLES=ON -DJUCE_BUILD_EXTRAS=ON
cmake --build cmake-build --target DemoRunner

Minimum System Requirements

Building JUCE Projects

• C++ Standard: 17
• macOS/iOS: Xcode 12.4 (Intel macOS 10.15.4, Apple Silicon macOS 11.0)
• Windows: Visual Studio 2019 (Windows 10)
• Linux: g++ 7.0 or Clang 6.0 (for a full list of dependencies, see here).
• Android: Android Studio (NDK 26) on Windows, macOS or Linux

Deployment Targets

• macOS: macOS 10.11
• Windows: Windows 10
• Linux: Mainstream Linux distributions
• iOS: iOS 12
• Android: Android 5 - Lollipop (API Level 21)

Contributing

Please see our contribution guidelines.

Licensing

See LICENSE.md for licensing and dependency information.

AAX Plug-Ins

AAX plug-ins need to be digitally signed using PACE Anti-Piracy's signing tools before they will run in commercially available versions of Pro Tools. These tools are provided free of charge by Avid. Before obtaining the signing tools, you will need to use a special build of Pro Tools, called Pro Tools Developer, to test your unsigned plug-ins. The steps to obtain Pro Tools Developer are:

1. Sign up as an AAX Developer here.
2. Request a Pro Tools Developer Bundle activation code by sending an email to [e-mail].
3. Download the latest Pro Tools Developer build from your Avid Developer account.

When your plug-ins have been tested and debugged in Pro Tools Developer, and you are ready to digitally sign them, please send an email to [e-mail] with the subject "PACE Eden Signing Tools Request". You need to include an overview of each plug-in along with a screen recording showing the plug-in running in Pro Tools Developer, with audio if possible.

Please also include the following information:

• Company name
• Admin full name
• Telephone number

Once the request is submitted, PACE Anti-Piracy will contact you directly with information about signing your plug-ins. When the plug-ins have been signed, you are free to sell and distribute them. If you are interested in selling your plug-ins on the Avid Marketplace, please send an email to [e-mail].