Simone Ruffini

These are the setting:  They are pretty autoesplicative

Yes, I was talking about cmake file, but I can't make it work. This is my CMakeLists.txt file ```cmake # Necessary tag cmake_minimum_required(VERSION 3.16) cmake_path(SET STM32_CUBE_F4_PATH "./") set(CMAKE_TOOLCHAIN_FILE ${CMAKE_CURRENT_SOURCE_DIR}/Lib/stm32-cmake/cmake/stm32_gcc.cmake) project(tlb_battery)...

Unfortunately I have a use case where the development team can't change the way it used to work. Since the stm32-vscode plugin does that in the make file I need...

I would mention #315 as a way to auto-define what peripheral needs to be compiled and what not? Can the user just comments out the used peripherals in `stm32fxx_hal_conf.h` and...

Yes I'm comfortable with cmake but my team uses CubeMX for code generation. For now this is not a problem because stm32-cmake can be used alongside CubeMX. My previous example...

My use case is to have a somewhat stable CMAkeList file that needs little change from projet to project (the developer must learn cmake but not the library so much...

I would like to add that if you use a tool like STM32 CubeMX it automatically does that for you: changing the `stm32fxxx_hal_conf.h` file with the correctly enabled peripherals.

What's the status of this PR? I'm interested in it being merged

So we are missing unit test and it can be merged?

If the original author of the PR doesn't rebase, can someone else do it?