Skip to content

Fix BoardContext compilation break on develop#36

Merged
emrainey merged 1 commit into
developfrom
issue-35
Jun 27, 2026
Merged

Fix BoardContext compilation break on develop#36
emrainey merged 1 commit into
developfrom
issue-35

Conversation

@emrainey

Copy link
Copy Markdown
Owner

This PR fixes the compilation break of the target/board libraries on the develop branch.

Changes

  • Included <cortex/linker.hpp> in BoardContext.cpp to correctly define the LINKER_TYPED_SYMBOL macro.
  • Commented out the premature GetEthernet() declaration in BoardContext.hpp and its enlistment in GlobalContext.cpp since the network stack files are not yet present on develop.
  • Removed the unused jarnax/net/ethernet/Driver.hpp header inclusion from Demo.hpp.

Closes #35

Related To Issue: 35

What's Wrong:
* Compilation of BoardContext failed on develop because BoardContext.cpp declared linker symbols using the LINKER_TYPED_SYMBOL macro, but did not include the <cortex/linker.hpp> header where the macro is defined.
* BoardContext.hpp declared GetEthernet() and GlobalContext.cpp enlisted it in the SuperLoop, but the net/ethernet module and headers are not yet present on develop, causing compile-time errors.

How Was it Fixed (if not obvious):
* Included <cortex/linker.hpp> in BoardContext.cpp to define LINKER_TYPED_SYMBOL.
* Commented out the GetEthernet() declaration in BoardContext.hpp and its enlistment in GlobalContext.cpp until the net module is merged.
* Removed the unused jarnax/net/ethernet/Driver.hpp header inclusion from Demo.hpp.
* AI generated the header inclusion additions and commented out the premature references, while a human reviewed the changes and executed the builds and tests.

What side effects does this have (could be none):
* None. Fixes compilation errors for targets compiled under host native presets.

Which builds did you run to make sure they build?
[x] arm-none-eabi-gcc Cortex M4
[x] arm-none-eabi-gcc Cortex M7
[x] (Apple) Native Clang
[ ] (Apple) Homebrew GCC
[x] (Apple) Homebrew LLVM

How Do We Know and Can Show It's Fixed:
* Host-native unit tests in all active suites compile and pass successfully.

Which Unittest Series did you Check?
[x] (Apple) Homebrew LLVM

Did this affect any on-target builds? If so which were tested?
[x] STM32H753ZI board
@emrainey

Copy link
Copy Markdown
Owner Author

build-all-presets.py Execution Results

The script was run locally to verify all configurations:

  • on-target-cortex-m4-gcc-arm-none-eabi: ✅ Passed
  • on-target-cortex-m7-gcc-arm-none-eabi: ✅ Passed
  • on-host-native-clang: ✅ Passed
  • on-host-native-llvm: ✅ Passed
  • on-host-native-gcc: ❌ Failed (Pre-existing/unrelated issue on macOS host where the -stdlib=libc++ flag causes Homebrew GCC g++-13 to fail to locate standard C++ headers like <cstddef>).

@emrainey emrainey merged commit 8587382 into develop Jun 27, 2026
4 checks passed
@emrainey emrainey deleted the issue-35 branch June 27, 2026 02:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant