PlatformIO + JUCE: Mac CMake issue

Hi all.

I’m running a PlatformIO project in CLion, and I’m using CMakeListsUser.txt to include config for a JUCE project:

# CMakeListsUser.txt
if (NOT CMAKE_BUILD_TYPE MATCHES "[platformio-env]")
    # Unset some stuff set by pio; allow JUCE to set these to its own liking.

    # pio sets CMAKE_SYSTEM_NAME to 'Generic'; update this for JUCE's benefit.

endif ()

wfs-controller/CMakeLists.txt is a regular JUCE CMake file

cmake_minimum_required(VERSION 3.15)
list(APPEND CMAKE_PREFIX_PATH ~/.local/share/JUCE)
juce_add_gui_app(WfsController PRODUCT_NAME "WFS Controller")
# etc.

And for Linux this works just fine; I can switch between PlatformIO and JUCE configurations in CLion :seal::lion::raised_hands:

Mac trouble

On OSX (10.13 I’m afraid, for reasons of ancient hardware), CMake fails to find various system frameworks, e.g.:

CMake Error at /Users/tar/.local/share/JUCE/lib/cmake/JUCE-6.1.6/JUCEModuleSupport.cmake:281 (find_library):
  Could not find juce_found_Accelerate using the following names: Accelerate
Call Stack (most recent call first):
  /Users/tar/.local/share/JUCE/lib/cmake/JUCE-6.1.6/JUCEModuleSupport.cmake:537 (_juce_link_frameworks)
  /Users/tar/.local/share/JUCE/lib/cmake/JUCE-6.1.6/JUCEConfig.cmake:111 (juce_add_module)
  wfs-controller/CMakeLists.txt:27 (find_package)

Conditionally adding list(APPEND CMAKE_PREFIX_PATH /System/Library/Frameworks) for CMAKE_SYSTEM_NAME STREQUAL "Darwin" kind of gets around that, though CMake doesn’t seem completely happy, e.g.:

"/System/Library/Frameworks/Accelerate.framework".  Targets may link only
  to libraries.  CMake is dropping the item.

Still, it completes configuration and I can attempt a build, but then the compiler chokes on a mouthful of Objective-C, e.g.:

In file included from ~/.local/share/JUCE/include/JUCE-6.1.6/modules/juce_events/juce_events.cpp:42:
In file included from ~/.local/share/JUCE/include/JUCE-6.1.6/modules/juce_events/juce_events.h:52:
In file included from ~/.local/share/JUCE/include/JUCE-6.1.6/modules/juce_core/juce_core.h:197:
In file included from ~/.local/share/JUCE/include/JUCE-6.1.6/modules/juce_core/native/juce_BasicNativeHeaders.h:45:
In file included from /System/Library/Frameworks/Cocoa.framework/Headers/Cocoa.h:12:
In file included from /System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:8:
/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:503:1: error: expected unqualified-id
@class NSString, Protocol;

(NB I’m using JUCE 6.1.6 because I’m stuck with the 10.13 SDK… if there is in fact a way to switch to JUCE 7 and target 10.13 I’d be keen to hear.)

So my guess is mixing pio and JUCE like this, on Mac at least, means some paths or CMake/compiler flags are missing or invalid where JUCE needs them. If anyone has any suggestions re. getting this to work (as it does on Linux) I’d be very grateful for the assistance.

Two things:

  1. Accelerate.framework is a requirement, no? On MacOS 10.13 it used to be called the ‘vecLib’, if I recall correctly … either way removing this dependency is a tricky road to take.

  2. Very interested in why you’re porting JUCE to be used in the PlatformIO environment … got it running on ESP32? :slight_smile:

Hah, I wish I could say that what I’m trying to do is as interesting as that! (Apologies for having given an ambiguous impression above.) I have a collection of networked Teensy 4.1’s running a distributed wave field synthesis algorithm, and a JUCE-based WFS controller (running on a regular, general-purpose computer) sending audio and control data to the Teensies.

The problem is mostly one of convenience – being able to configure both the platformIO and JUCE builds from a single CMake project. As described, this works on Linux, but (for the combination of OSX 10.13 and JUCE 6.1.6 at least) not on Mac at present.