![]() ![]() Upx -1 /myApp/Contents/MacOS/myAppThat's all ! The app is now supported by Big Sur and can be launched directly :-) Upx -d /myApp/Contents/MacOS/myApp2) Re-compress the app, but at the minimum level to preserve compatibility with Big Sur : To get around all these constraints I did some manipulations in a less aggressive environment, namely a Mojave virtual machine that I had to create for the occasion (Catalina would perhaps also be suitable.). That said, it is possible to see that the compression with UPX must be kept, otherwise the application (its Unix executable in fact) that has been decompressed will instantly disappear from the screen. I've been going round and round in circles, and I've come to believe that the problem is not about Big Sur giving permission to the application, but more likely a problem between UPX (since we're talking about an application compressed with upx) and Big Sur. ![]() ![]() I've been struggling for a few days now, but I've just found a solution that worked in my case. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |