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.

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

llext: move settings away from cmake/compiler/* files #72812

Open
pillo79 opened this issue May 15, 2024 · 0 comments
Open

llext: move settings away from cmake/compiler/* files #72812

pillo79 opened this issue May 15, 2024 · 0 comments
Labels

Comments

@pillo79
Copy link
Collaborator

pillo79 commented May 15, 2024

Is your enhancement proposal related to a problem? Please describe.

PR #69831 adds the llext-edk build target, and uses the same location for configuration as llext itself: the files in the cmake/compiler/* subdirectories.
As discussed in this comment and related thread, this location is arguably acceptable for llext (since it's used for the current build), but definitely not for llext-edk, where the external compiler might be very different from the one used by Zephyr.

Describe the solution you'd like

The refactor is simple, once we figure out a location and storage criteria that satisfies the following constraints:

  • It makes sense to keep llext and llext-edk settings grouped together
  • They should be separated from other parameters related to the current build of the main Zephyr code
  • These settings are architecture- and compiler- specific; however:
    • the llext settings refer to the same compiler used by the Zephyr build
    • the llext-edk settings are exported in a set of build files, and as such may refer to a different compiler

Ideas are welcome!

@pillo79 pillo79 added Enhancement Changes/Updates/Additions to existing features area: Build System area: Linkable Loadable Extensions labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant