Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'binary size'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Staff and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.5 Beta New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 1 result

  1. "Optimised for M1". And a quick check of the app bundle size on Mac confirmed what we've feared: "the return of the fat binaries". Each binary (Photo, Publisher and Designer) is now at least 2.7 GB (!) in size each - from a previous 1.7 GB, if I remember correctly. Which is already way too much, but oh well. And a quick checks confirms that, e.g. lipo -info /Applications/Affinity\ Photo.app/Contents/MacOS/Affinity\ Photo Architectures in the fat file: /Applications/Affinity Photo.app/Contents/MacOS/Affinity Photo are: x86_64 arm64 Now this is of course only the "main" binary, and each provided framework now comes for two architectures. According to https://eclecticlight.co/2020/07/30/instant-weight-loss-how-to-strip-universal-apps/ it should be possible to strip away the unnecessary architecture (arm64 in my case), to slim down the binary size to approximately 1.7 GB in this case (give or take additional space for new features, although I don't think there are any new features except the new binary for ARM aka "Apple Silicon"), without breaking the code signature. However I am not going to do that right now, unless someone has already done this and possibly has an automated way to strip away the ARM64 architecture for all binaries and libraries within a given app bundle on Mac? But let's face it: 1.7 GB is already way too much: it's not like those apps come with tons of graphic resources (like textures, brushes, or even video tutorials etc.) which would justify that enormous disk space being used.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.