Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Evaluate lighter strategies for binary size impact #30

Open
marinofelipe opened this issue Dec 31, 2021 · 1 comment
Open

Evaluate lighter strategies for binary size impact #30

marinofelipe opened this issue Dec 31, 2021 · 1 comment
Assignees
@marinofelipe
Labels
enhancement New feature or request

Comments

@marinofelipe
Copy link
Owner

Evaluate other strategies for binary size calculation, such as checking the generated products.
Goal is to understand and later decide how each strategy stands in terms of cost (performance hit) versus accuracy of result.
@marinofelipe marinofelipe added the enhancement New feature or request label Dec 31, 2021
@marinofelipe
Copy link
Owner Author

@marinofelipe to check how debug/release built products stacks against the current heavy archive strategy.
The API could be tweaked to allow a derived data path to be passed for a lighter binary size calculation.

@marinofelipe marinofelipe self-assigned this Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marinofelipe marinofelipe

Labels
enhancement New feature or request
Projects
Open tasks
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
1 participant
@marinofelipe