Migrate ThreadX RTOS to Bazel build system#501
Draft
SuhashiniNaik wants to merge 1 commit into
Draft
Conversation
New BUILD files: - libs/3rdparty/threadx: Core ThreadX library with label_flags for port, port_impl, os_hooks and core_configuration selection - libs/bsw/asyncThreadX: async_threadx, async_threadx_impl and threadx_configuration targets with threadx_core_configuration label_flag - platforms/s32k1xx/3rdparty/threadx: Cortex-M4 port implementation and port headers for s32k148 - platforms/posix/3rdparty/threadx: Linux port implementation and port headers for POSIX - executables/referenceApp/platforms/s32k148evb/main: threadx_os_hooks - executables/referenceApp/platforms/s32k148evb/threadXCoreConfiguration - executables/referenceApp/platforms/posix/threadXCoreConfiguration Modified BUILD files: - libs/bsw/async: Added support_threadx branch to async_platform_default - platforms/s32k1xx/bsp/bspInterruptsImpl: Added threadx RTOS headers and wired into bsp_interrupts_impl_rtos_hdrs alias - platforms/posix/bsp/bspInterruptsImpl: Added threadx variant Key Bazel patterns used: - - label_flag + alias + select() for platform/RTOS-specific selection - target_compatible_with to restrict platform-specific targets - async_threadx_impl and async_freertos_impl marked incompatible for opposite RTOS configs to prevent build failures in bazel build //... - Circular dependency threadX -> osHooks -> asyncThreadX -> threadX broken by depending on threadx_headers instead of threadx Added --config=s32k148_threadx to .bazelrc combining s32k148 platform and threadx RTOS flag. Suggest adding this as a CI step: bazel build --config=s32k148_threadx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Migrate ThreadX RTOS to Bazel build system
New BUILD files:
port, port_impl, os_hooks and core_configuration selection
threadx_configuration targets with threadx_core_configuration
label_flag
port headers for POSIX
Modified BUILD files:
and wired into bsp_interrupts_impl_rtos_hdrs alias
Key Bazel patterns used:
opposite RTOS configs to prevent build failures in bazel build //...
broken by depending on threadx_headers instead of threadx
Added --config=s32k148_threadx to .bazelrc combining s32k148 platform
and threadx RTOS flag.