Improve Msg Function Registration for Module Tracking #3425
Assignees
Comments
github-merge-queue bot
pushed a commit
that referenced
this issue
Jul 10, 2024
…3424) * Only register Msg functions with a module name With the `saveUsedModules` flag, we only want to be tracking modules that can actually be included/excluded to avoid duplicating function headers for those functions that are always included by default. By explicitly checking if the module name includes "Msg", we can skip this for cases like `GenSymIO` which are always included and was causing build issues with the module generation script. * Add registration without module name
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This pull request refines the logic for registering message-related functions (Msg functions) within the context of the saveUsedModules flag.
The
saveUsedModulesflag tracks modules that can be selectively included or excluded during the build process. However, including functions whose corresponding modules are always included by default creates unnecessary duplication in the generated function headers.This PR introduces an explicit check to identify Msg functions with module names containing "Msg". These functions are skipped during registration, as their corresponding modules are inherently part of the build.
This will:
saveUsedModulesaccurately reflects modules subject to inclusion/exclusionThe text was updated successfully, but these errors were encountered: