fix: local build on macOS or other platform

[ruattd]

Now macOS can build the app locally, but I'm not sure whether the changes will affect CI build. Most likely not.
By the way, it seems ./run libs native is not necessary for assembleDebug now.

Summary by Sourcery

Add support for building the app on macOS.

New Features:

• Enable local builds on macOS.

Enhancements:

• Simplify the Gradle build command.

Build:

• Update build instructions to include macOS and Arch Linux.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request enables local builds on macOS, adds support for Arch Linux, and updates build commands. It also modifies the Android SDK version and removes an unnecessary build step.

Flow diagram for updated build process

flowchart TB
    start[Start Build] --> checkOS{Check OS}
    checkOS -->|macOS| installXcode[Install Xcode Tools]
    checkOS -->|Linux| skipXcode[Skip Xcode Install]
    installXcode --> installTools[Install Required Tools]
    skipXcode --> installTools
    installTools --> installSDK[Install Android SDK Components]
    installSDK --> buildGradle[Build with Gradle]
    buildGradle --> assembleBuild[assemble Debug/Release]
    assembleBuild --> done[Done]

Loading

File-Level Changes

Change	Details	Files
Added macOS and Arch Linux support for local builds	Added instructions for installing necessary tools on macOS and Arch Linux. Updated the list of supported operating systems to include macOS and Arch Linux.	README.md
Updated Android SDK version and build commands	Updated the required Android SDK version. Modified Gradle build command. Removed unnecessary ./run libs native step for assembleDebug command.	README.md TMessagesProj/build.gradle
Fixed build script compatibility issue	Updated build scripts to use the correct LLVM prefix based on the build platform.	TMessagesProj/jni/build_dav1d_clang.sh TMessagesProj/jni/build_ffmpeg_clang.sh TMessagesProj/jni/build_libvpx_clang.sh
Fixed file copy command in patch script	Corrected the file copy command to handle filenames with spaces correctly.	TMessagesProj/jni/patch_ffmpeg.sh

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @ruattd - I've reviewed your changes - here's some feedback:

Overall Comments:

• Please explain why the debug signing configuration was commented out. If this is necessary for macOS builds, it should be documented.
• The PR description mentions uncertainty about CI impact. Please verify that these changes don't break CI builds before merging.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}