ESP32 Forum

I just updated from Mojave to Big Sur and my 3.2-based legacy project no longer builds because of all the issues with xtensa tools not being from an authorized developer. I've had a surprisingly tough time finding the solution online . The apple suggestion for handling this is by doing a ctrl-open on each application and selecting "Open" in the dialog, which is painful but works until I get to the shared object libraries which cannot be opened.

How did people get around this?

Thanks

Not sure if it's the right model, but after the liblto_plugin.so was blocked, in could allow it to run in System Preferences->Security Privacy -> General.

Seems pretty hacky though.

OSX Catalina was the last version I got to work.
Big Sur is locked down to the point of being pretty useless for our tool chains/apps.
I Dual boot.