Skip to content
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.

Sign up for GitHub

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

Spelling Mistakes Updated #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Spelling Mistakes Updated #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,9 @@ Contents:


<br>
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.



Expand Down