diff --git a/README.md b/README.md index 589673f..9ea6aed 100644 --- a/README.md +++ b/README.md @@ -17,9 +17,9 @@ Contents:
-STM libraries, headers, and samples have been modified to work with GNU Tools for ARM Embedded Processors toolchain and STM32F4 Discovery EVB. Generally this just involved adding Makefiles and a slightly modified version of the TrueStudio linker file. In the Project directory, everything under Demonstration, FW\_upgrade, and Peripheral\_Examples is buildable from the command line by running 'make' +STM libraries, headers, and samples have been modified to work with GNU Tools for ARM Embedded Processors toolchain and STM32F4 Discovery EVB. Generally, this just involved adding Makefiles and a slightly modified version of the TrueStudio linker file. In the Project directory, everything under Demonstration, FW\_upgrade, and Peripheral\_Examples is buildable from the command line by running 'make'. -STM's approach toward 'library code' is somewhat non-traditional. Rather than building libraries up front and linking them with your source, STM appears to intend for you to include their individual source files in your code's build. Some of their source files include local headers and modules (i.e. stm32f4xx\_conf.h, stm32f4xx\_it.c/h, system\_stm32f4xx.c, etc) that you modify/store in your source tree. Because of this, building the library up front wouldn't work properly, as the configuration for some library modules could vary from project to project. +STM's approach toward 'library code' is somewhat non-traditional. Rather than building libraries upfront and linking them with your source, STM appears to intend for you to include their source files in your code's build. Some of their source files include local headers and modules (i.e. stm32f4xx_conf.h, stm32f4xx_it.c/h, system_stm32f4xx.c, etc) that you modify/store in your source tree. Because of this, building the library upfront wouldn't work properly, as the configuration for some library modules could vary from project to project.