feat: Changing the build system to cmake #1
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Piraterna/aurix#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Switching to cmake would be a more "proper" build system. This allows the user to easily change custom "targets" aka toolchain files (https://cmake.org/cmake/help/latest/envvar/CMAKE_TOOLCHAIN_FILE.html). And also using ninja (https://ninja-build.org/) would be a great idea too since it’s faster then make. Also a proper system to configure aurix and build (using like bash scripts). This is what I do in leaf and is totally a personal preference but I think it’s wise to switch since it’s easier to scale the project. If you need any help I would be more then happy to help!
I'm still a bit worried about switching to CMake fully - especially making sure the entire system is easily expandable for other architectures and easy to understand. I'll probably make a new branch to do some experiments with CMake.
Yep i fully understand but i honestly think cmake syntax is easier to understand then make. And for other architectures you could do as i said in the first comment. Use toolchain files. In leaf i also have like a gen-$bootloader.sh script to generate the final image. So the configure and build system uses the cmake to configure and ninja to build then makes a image with a predefined script based on arch and bootloader. And i think a new branch would be wise. I would love to help
Closing for settling with Make.
@schkwve fair enough.