Skip to content

[FEATURE] move debug and optimization to global configs in cmake #3467

Open

Description

@cujomalainey

Is your feature request related to a problem? Please describe.
Allow optimizations to be globally configurable, as they should be, we should not be enforcing anything on the developer

Describe the solution you'd like
move to cmake vars/env vars

Describe alternatives you've considered
none

Additional context
#3458 (comment)

Activity

  1. added this to the v1.7 milestone on Sep 25, 2020
  2. lgirdwood commented on Sep 25, 2020

    @lgirdwood
    Member
  3. lgirdwood commented on Jan 12, 2021

    @lgirdwood
    Member

    @cujomalainey I guess this is still WIP since Janusz has left Intel ? IIRC I've seen one or two PRs to help here but assume we need more ?

  4. cujomalainey commented on Jan 13, 2021

    @cujomalainey
    ContributorAuthor

    I think we can do more work on this once we stop running Cmakes both with and without kconfig. If it's only with kconfig values set then we can adjust things as necessary

  5. lgirdwood commented on Jan 14, 2021

    @lgirdwood
    Member

    @cujomalainey I think we have the global debug/optimisation configs in kconfig today but there may be one or tow places where it's hard coded in cmake. Would using only kconfig work here for you to set the cmake vars ?

  6. cujomalainey commented on Jan 15, 2021

    @cujomalainey
    ContributorAuthor

    Thanks, once #3617 is complete i can go around and fixup hardcoded flags where i find them

  7. lgirdwood commented on Jan 18, 2021

    @lgirdwood
    Member

    @marc-hb do you think you can fix #3617 this week ?

  8. marc-hb commented on Jan 19, 2021

    @marc-hb
    Collaborator

    I don't think so, sorry. I had a very quick look a long time ago and it seemed to require significant CMake surgery. I'm familiar with CMake but not with our CMakeLists.txt files.

  9. bkokoszx commented on Jan 27, 2021

    @bkokoszx
    Collaborator

    @cujomalainey Regarding #3467 (comment) comment - will you be able to take a look at this after #3617 gets merged?

  10. cujomalainey commented on Jan 27, 2021

    @cujomalainey
    ContributorAuthor

    Yes, this should be much easier

  11. lgirdwood commented on May 10, 2021

    @lgirdwood
    Member

    Aim is to align with how Zephyr set configuration. More of this will align in v1.9

  12. modified the milestones: v1.7, v1.9 on May 10, 2021
  13. marc-hb commented on May 10, 2021

    @marc-hb
    Collaborator

    Just for the record: Zephyr does not use CMAKE_BUILD_TYPE.

    (and .config change #3617 has been merged for some time)

  14. modified the milestones: v1.9, v2.7 on Feb 15, 2023
  15. modified the milestones: v2.7, TBD on Aug 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions