✨ Initial support for low powered devices with other architectures #567
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tectures (#566) - Add 2 profiles with binary size reduction feature to allow devices with low storage to compile/build the app with smaller size. - Add 3 profiles to allow devices with low powered cpus or other architectures like arm to compile apps using less cpu usage. - Add 6 profiles with hybrid of both for both low powered cpu and low storage devices.
…devices-with-other-architectures
…devices-with-other-architectures
…devices-with-other-architectures
alamin655
approved these changes
Sep 2, 2024
mergify
bot
deleted the
FEAT/566_initial-support-for-low-powered-devices-with-other-architectures
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR provides initial support for low powered devices with other architectures by providing different cargo profiles to fit different needs.
The profiles that are provided are as follows:
Why is this change important?
The reason behind including these changes is to lay the initial groundwork of foundational support for low powered devices with other architectures, and which can be in future leveraged to expand support of the app to other architectures with further improvements and features provided in the code geared towards this.
How to test this PR locally?
It can be tested by installing and running Websurfx as mentioned in the
docsand on thereadmeand by launching the browser and thoroughly testing. By first building the app with one profiles provided by this PR by running the following command:cargo build --profile "<the profile name>"Author's checklist
v1.17.0.Related issues
Closes #566