[FW-50] Make the template compile with the mock #425
Merged
Conversation
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
…iginal or the mock sources and fix the includes
g0nz4I0
reviewed
Oct 24, 2024
Member
g0nz4I0
left a comment
g0nz4I0
left a comment
There was a problem hiding this comment.
still doesnt compile I believe due to ARM inlined assembly
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds support for both compilation for the simulator on the host target (linux support only) or for the MCU. The compilation is configured by passing the
-simflag with either "ON" or "OFF" to the pythonbuild.pyscript or by calling CMake with-DSIMULATE=TRUEor-DSIMULATE=FALSE.The code for the simulator still doesn't compiles because there are still includes from the hal, wich cannot be compiled for the host architecture (it has ASM instructions for the ARM MCU embedded in the code). That should be fixed once all modules are converted, but will take too much for the scope of this PR.
Also the vscode config files have been updated to reflect the changes and the build script now chooses the output path based on the options selected, so that the incremental build is more useful if for example the ST-LIB is first compiled for a project with ethernet and then recompiled for a project without ethernet.