Build failure - macOS 11.0 Deprecations

[ctreleaven]

I'm attempting to add OpenShot to the MacPorts repository. I'm building from the v0.2.0 tarball from github.

libopenshot-audio failed to build on our macOS 11.0 buildbot due to the use of several deprecated functions. Eg:

In file included from /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_multimedia_libopenshot-audio/libopenshot-audio/work/libopenshot-audio-0.2.0/JuceLibraryCode/modules/juce_audio_devices/juce_audio_devices.cpp:189: /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_multimedia_libopenshot-audio/libopenshot-audio/work/libopenshot-audio-0.2.0/JuceLibraryCode/modules/juce_audio_devices/native/juce_mac_CoreAudio.cpp:55:13: warning: 'AudioHardwareServiceHasProperty' is deprecated: first deprecated in macOS 10.11 - no longer supported [-Wdeprecated-declarations] if (AudioHardwareServiceHasProperty (kAudioObjectSystemObject, &addr)) ^ The log file is available online for the next couple of weeks at: https://build.macports.org/builders/ports-11_arm64-builder/builds/9083

BTW, this happens to be an Apple Silicone based buildbot.

Steps to reproduce the behavior: See log file attached.

Expected behavior: Successful build.

System Details: libopenshot-audio v 0.2.0 macOS 11.0

Log Files: Attached

Exception / Stacktrace: n/a

Screenshots: (Optional) n/a

libopenshot audio build fail macOS 11.0 .log

[ctreleaven]

Ping!

[stale[bot]]

Thank you so much for submitting an issue to help improve OpenShot Video Editor. We are sorry about this, but this particular issue has gone unnoticed for quite some time. To help keep the OpenShot GitHub Issue Tracker organized and focused, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.

This issue will be closed, as it meets the following criteria:

• No activity in the past 90 days
• No one is assigned to this issue

We'd like to ask you to help us out and determine whether this issue should be reopened.

• If this issue is reporting a bug, please can you attempt to reproduce on the latest daily build to help us to understand whether the bug still needs our attention.
• If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.

Thanks again for your help!