Skip to content

Sets PICO_DEOPTIMIZED_DEBUG to be enabled by default #1621

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.

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

Conversation

recursivenomad
Copy link
Contributor

Optimizing a debug build with PICO_DEOPTIMIZED DEBUG disabled (the current default) results in breakpoints not being possible in certain functions. This change makes the default behaviour of PICO_DEOPTIMIZED_DEBUG to be enabled, so that debug builds will fully work as expected when no explicit value for the option is passed.

Since the cache stores the default value of PICO_DEOPTIMIZED DEBUG, you will need to delete the CMakeCache.txt previously generated in your project directory for this change to default behaviour to take effect in existing projects.

This commit is related to pull request #1620 in the primary repository.

See Issue #1618 in the primary repository for additional context.

Optimizing a debug build with PICO_DEOPTIMIZED DEBUG disabled (the current default) results in breakpoints not being possible in certain functions.  This change makes the default behaviour of PICO_DEOPTIMIZED_DEBUG to be enabled, so that debug builds will fully work as expected when no explicit value for the option is passed.

Since the cache stores the default value of PICO_DEOPTIMIZED DEBUG, you will need to delete the CMakeCache.txt previously generated in your project directory for this change to default behaviour to take effect in existing projects.

This commit is related to pull request raspberrypi#1620 in the primary repository.

See Issue raspberrpi#1618 in the primary repository for additional context.
@recursivenomad
Copy link
Contributor Author

(I acknowledge that this change may be controversial as it changes the default optimization of debug builds, so please consider this pull request with caution)

@kilograham kilograham marked this pull request as draft May 20, 2024 00:27
@kilograham
Copy link
Contributor

converting to draft as we likely will not doing this (still open for now)

@kilograham kilograham added this to the none milestone May 20, 2024
@recursivenomad
Copy link
Contributor Author

Hi @kilograham - Checking in a few months later if you'd like me to update/preserve this PR? I still like the idea of a debug build providing all debug features by default, but I understand if it is not what the SDK team considers ideal.

If the PR is confidently not needed, I will delete the fork to reduce clutter.

@kilograham
Copy link
Contributor

yes; i don't think we will make this the default, so feel free to delete

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants