Implement new CMakeLists.txt
generation backend (cbuild2cmake)
#1237
Labels
cmake-backend
Issues that will be solved by the new CMake-backend
enhancement
New feature or request
As a result of the investigation tracked in #1044 the new
CMakeLists.txt
generation backend should be planned and implemented according to the CMakeLists Proposal.Work breakdown structure
go
test cases must be implemented#1✔️csolution
cbuild-idx.yml
#1272✔️intdir
: in the multi-context scenario a solution level intermediate directory is neededcsolution.yml
andcproject.yml
in the form ofexecutes
nodesproject
nodes to acceptcmake [generic|standalone]
,input
andoutput
to handle the integration of generic CMake libraries as well as standalone CMake projectscbuild2cmake
cbuild-idx.yml
andcbuild.yml
files#2,#21✔️#3,#22✔️CMakeLists.txt
making use of CMakeExternalProject
features, set step dependencies and by-products, database generation#4#62✔️CMakeLists.txt
,groups.cmake
andcomponents.cmake
files considering compile options as welllanguages
andscope
#5✔️<toolchain>.cmake
file#65✔️#29✔️#31✔️#32✔️#33✔️#35✔️#36✔️#37✔️cbuild
cbuild
front-end to optionally callcbuild2cmake
instead ofcbuildgen
#165✔️CMSIS-Toolbox
to incorporate the new binarycbuild2cmake
#1398✔️cpackget
,cbuild
,csolution
andcbridge
, allowing future removal of the current Build ManagerCMSIS-Pack-Utils
for CMSIS Packs consumption from CMakeThe text was updated successfully, but these errors were encountered: