-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
CMake Cross-compilation for baremetal target #7281
Comments
@alexreinking @steven-johnson may I ask you to review the PRs, please? |
Definitely! Thank you for what appears to be a major contribution! |
The CMake-specific changes are better handled by @alexreinking, I've assigned them to him. |
For Issue 6, I've added |
I appreciate for your quick feedback! I will have a look and update. |
Now that HelloBaremeal works, I will close this item and leave the remaining further rework to #7344 |
Background
As mentioned in README_cmake, Cross-compiling in CMake can be tricky, since CMake doesn't easily support compiling for both the host platform and the cross-platform within the same build. This gets more tricky when we target baremetal environment, where the application is built by somehow uncommon toolchain and the runtime runs without or limited OS support. Thus, we often end up with hacky workaround, which, as one can imagine, makes the build system inflexible and easy to break when updating. Also, I would assume this is probably raising the bar for users.
In this ticket, I'd like to address the identified issues in existing CMake build and bring proposal solutions for discussion.
Issues
Threads
library as mandatory, which some of the baremetal toolchain doesn't have.add_halide_runtime()
doesn't work with cross-compiler toolchainadd_halide_generator()
has an issue in exporting/importing the generator as packagetutorial/
norapps/
from which users can learn quickly how to write CMake to cross-compile app with Halide.The text was updated successfully, but these errors were encountered: