What the library files in 32 are used for

The library is equivalent to the warehouse, the library file is a collection of some commonly used ** component dll files, and so many dll files in windows are library files. The library file can be divided into the library file at the time of development, and the library file that runs officially after development (can be called the service version of the library file), the library file of the development version, there are many files, including a lot of useful **, the library file of the service version, which is only used to ensure normal operation. Fewer documents.

To be honest, the question is rather vague.

However, from a programming point of view, there are usually static and dynamic libraries. Windows static library files are. lib file, dynamic library file is.

dll file. The content is the same, it is to encapsulate functions together and compile them for yourself or others to call. The advantage is that the compiled library file cannot see the source** and can be kept confidential; At the same time, there will be no problems due to accidentally modifying the function, which is easy to maintain.

The difference between the two types of libraries is that static libraries are loaded directly into memory when they are called, while dynamic libraries are loaded into memory when they are needed and released from memory when they are not in use.

The suffixes for static and dynamic libraries are respectively. a and. I don't know if it answers your question?

It's all peripherals, what clocks, io, withered tim, uart....All of its peripherals and kernels have corresponding libraries, just a little more. What you want to use depends on your own needs.

Configuration and use of each function module.

The STM32 firmware library is the configuration and use of each functional module. Similar to APIs, programs can be written by touching a few low-level layers. Improve development efficiency and lower the barrier to entry. The peripheral library is only a part of the firmware library.

In addition, peripheral libraries, CMSIS, DSP libraries, and third-party drivers are combined to form a firmware library. The firmware serves the hardware and works with the driver to complete the interaction between software and hardware. The firmware provides a specification that can be compatible with different operating systems.

Configuration and use of STM32 functional modules. Similar to APIs, you can write programs with less contact with the bottom layer. Improve development efficiency and lower the barrier to entry. However, it is still recommended to read more datasheets, and only when you are familiar with the underlying layer can you write more efficient programs.

1 The vc++ directory generally includes header file directories, library file directories, reference directories, etc., which refer to public library directories such as SDKs and platform component libraries under System32, which is a collection form, of course, you can also add private header file directories, library file directories (static libraries), and reference directories (dynamic libraries).

2 The additional library items in the linker generally refer to static library files, which are generally used as references to export files that are implicitly called by private dynamic link libraries (DLLs). Generally, when the C++ private dynamic link library is generated, there are three files that need to be provided to the caller header file (*.).h), dynamic link library file (*.

dll), statically linked library files (*..)lib) This static library file is not a real static library file that contains all the programs, it is just an export file that contains only the exported symbols.

3 When there is a conflict between the public libraries in the vc++ directory, it is usually a few library files, and the ambiguity can be eliminated by ignoring the default library in the linker and attaching the public library you want to use.

These are all library files related to the chip function provided by ST company, which shields the underlying register operation, and only needs to call the functions in the library. For example, when applying ADC, you only need to use the functions in STM32F10X, which greatly reduces the difficulty of development.

This is a peripheral library file, for example, if you want to use an adc, you need to include these files about the adc. In general, which peripherals are used contain which related files. Hope to adopt!

The kernel-related files must include the csr folder inside the lib, which is the peripheral, which one to add (generally speaking, GPIO is of course used, and rcc is also required).

There are examples on this official library, for example, the official firmware library has a project file in the template directory under the project directory, which can be opened with mdk.

Gives you a project template. You have everything.

Because the STM32 version of the library function does not have a separate peripheral driver for NVIC (interrupt vector nesting) in the original version, the peripheral driver of NVIC is placed in it, which actually replaces the original STM32F10X

1. The header file contains the function declaration.

2. The import library records the address of the function in the dll, which is actually completely unnecessary and unnecessary, and m$ thinks it is more convenient to do so. In fact, the DLL file comes with a export table, and the function address can be found completely. Linux doesn't use this kind of thing.