Construction method of embedded ALSA library and embedded target board

Abstract

The invention provides a construction method of an embedded ALSA library and an embedded target board, and the construction method comprises the following steps: S1, editing a proc.conf file, and setting corresponding configuration information; s2, executing a make command, generating a Makefile, searching and checking an alsa-lib folder and an alsa-utils folder, and judging whether version files exist in the alsa-lib folder and the alsa-utils folder or not; s3, decompressing the corresponding version file into a Decode folder according to a judgment result, and compiling by utilizing a source code in the Decode folder to form a corresponding compiled file; and S4, outputting the compiled file to an out folder for storage. According to the method, different cross compilers are configured in advance by filling in the configuration file, and the required user space version and the alsa-utils version are selected for compiling during use, so that ALSA cross compiling selection of various different configurations and different cross compilers is realized, and the method is used for adapting to various different main application scenes.

Description

Technical Field

[0001] The present invention relates to the field of embedded systems, and particularly to a method for constructing an embedded ALSA library and an embedded target board. Background Art

[0002] ALSA, short for Advanced Linux Sound Architecture, is an ALSA under the Linux operating system, which is used to provide a unified audio interface. It is mainly used to provide a powerful and flexible audio and MIDI subsystem, enabling application programs and device drivers to interact with audio hardware in a unified manner. Its design includes a driver interface at the kernel level and a library and toolset in the user space. Developers can control parameters such as the sampling rate, number of channels, and volume of audio devices through ALSA, and can also implement functions such as input, output, and mixing of audio data.

[0003] In the Linux system, ALSA has become the standard audio architecture, and most of the audio algorithms and applications related to embedded systems rely on the ALSA interface to implement related functions. For developers, the use of the ALSA library is very convenient. It provides an alsa-lib folder to simplify application programming and provide more advanced functions. Compared with the original programming interface based on ioctl provided by OSS, the ALSA function library is more convenient to use. Using this function library, developers can develop their own application programs quickly and easily without paying too much attention to the underlying details. In addition, the ALSA library has the characteristic of multi-channel support, allowing application programs to process multiple audio streams simultaneously and perform independent control and processing on different channels, which is very useful in scenarios such as audio mixing, spatial processing, and audio recording. At the same time, the ALSA library is designed to support low-latency audio processing, which is crucial for real-time audio applications (such as audio editing software, games, and teleconferences). It is also because of these characteristics that the ALSA library plays an indispensable role in the development of linux embedded systems.

[0004] However, in the prior art, there are still several problems to be solved in the process of transplanting ALSA on an embedded board, such as how to quickly and conveniently cross-compile the ALSA library of the target board, the ALSA library version is prone to mismatch, and the problem of low work efficiency caused by frequently switching cross-compilers to adapt to different systems.

[0005] In view of the above problems existing in the prior art, there is an urgent need to design a method for constructing an embedded ALSA library to solve the above problems. Summary of the Invention

[0006] In order to overcome the technical problems existing in the prior art, the present application provides a method for constructing an embedded ALSA library and an embedded target board, so as to solve the problems raised in the above-mentioned background art.

[0007] The present application provides a method for constructing an embedded ALSA library, and the construction method includes the following steps:

[0008] Step S1: Edit the proc.conf file and set the corresponding configuration information, where the configuration information includes multiple cross-compiler version information, multiple version files required for the corresponding alsa-lib folders, determine whether the alsa-utils library needs to be compiled, and determine the corresponding required compilation platform options;

[0009] Step S2: Execute the make command to generate a Makefile file, search for and check the alsa-lib folder and the alsa-utils folder, and determine whether the version files exist in the alsa-lib folder and the alsa-utils folder;

[0010] Step S3: According to the determination result, decompress the corresponding version file into the Decode folder, and use the source code in the Decode folder for compilation to form a corresponding compilation file;

[0011] Step S4: Output the compilation file to the out folder for storage.

[0012] In some embodiments, step S4 further includes step S41: When the determination result is that the corresponding version file does not exist in the alsa-utils folder, automatically download the compressed package of the corresponding version file.

[0013] In some embodiments, the compressed package automatically synthesizes a corresponding download link through the url and is automatically downloaded into the alsa-utils folder.

[0014] In some embodiments, the downloaded compressed package is set to be automatically saved in the alsa-lib folder.

[0015] In some embodiments, the ALSA library includes a driver interface at the kernel level, a library and a toolset in the user space.

[0016] In some embodiments, the embedded ALSA library constructed by the construction method is applicable to any one of the x86 architecture, ARM architecture, and MIPS architecture.

[0017] The present application also provides an embedded target board, including:

[0018] A library directory and an embedded ALSA library, where the embedded ALSA library is built by the building method described in any of the above embodiments, and the embedded ALSA library is installed in the library directory.

[0019] Compared with the prior art, the beneficial effects of the present invention are as follows: For the rapid cross-compilation of the embedded ALSA library, the present application proposes a new compilation tool. This tool configures different cross-compilers in advance by filling in a configuration file. When in use, the required user space version and alsa-utils version are selected for compilation, so as to achieve multiple different configurations and the ALSA cross-compilation selection of different cross-compilers to adapt to a variety of different main application scenarios. The application scenarios mainly include: the situation where it is impossible to use platforms such as Buildroot and Yocto due to the need to separately configure and compile the ALSA library, the situation where an ALSA version needs to be selected to meet project conflicts, and the situation where multiple cross-compilers need to be managed to compile ALSA; in addition, by applying the method proposed in the present invention, multiple cross-compilers can be managed quickly, and the selection of different ALSA versions and the output of compilation results can be achieved efficiently and quickly, with higher and faster work efficiency. Description of the Drawings

[0020] Figure 1 It is a flowchart of a method for building an embedded ALSA library of the present application;

[0021] Figure 2 It is another flowchart of a method for building an embedded ALSA library of the present application;

[0022] Figure 3 It is a file tree diagram of a method for building an embedded ALSA library of the present application. Detailed Embodiments

[0023] The following specific embodiments illustrate the implementation manners of the present application. Those skilled in the art can easily understand other advantages and effects of the present application from the content disclosed in this specification. Although the description of the present application will be introduced in combination with some embodiments, this does not mean that the features of this application are limited to this implementation manner. On the contrary, the purpose of introducing the application in combination with the implementation manner is to cover other alternatives or modifications that may be extended based on the claims of the present application. In order to provide a deep understanding of the present application, many specific details will be included in the following description. The present application can also be implemented without using these details. In addition, in order to avoid confusing or obscuring the key points of the present application, some specific details will be omitted in the description. It should be noted that, without conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

[0024] It should be noted that in this specification, similar reference numerals and letters denote similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings.

[0025] This application provides a method for constructing an embedded ALSA library. Please refer to Figures 1 to 2 , and the construction method includes the following steps: Step S1: Edit the proc.conf file and set the corresponding configuration information, where the configuration information includes various cross-compiler version information, various version files required for the corresponding alsa-lib folders, determine whether the alsa-utils library needs to be compiled, and determine the corresponding required compilation platform options; Step S2: Execute the make command to generate the Makefile file, search for and check the alsa-lib folder and the alsa-utils folder, and determine whether there are version files in the alsa-lib folder and the alsa-utils folder; Step S3: According to the determination result, decompress the corresponding version file into the Decode folder, and use the source code in the Decode folder for compilation to form the corresponding compiled file; Step S4: Output the compiled file to the out folder for storage.

[0026] Specifically, when the construction method provided by this application is used, information such as multiple ALSA library versions and multiple cross-compiler versions will be pre-configured, and then the make command automatically checks the alsa-lib folder and the alsa-utils folder to determine whether there is a corresponding matching version library in the configured information, that is, whether the required version library exists in the local archive. If so, it automatically enters the next decompression process. If not, it enters the process of downloading the corresponding required information, and then enters the next decompression process.

[0027] In some embodiments, please refer to Figures 1 to 2 , Step S4 further includes Step S41: When it is determined that there is no corresponding version file in the alsa-utils folder, automatically download the compressed package of the corresponding version file.

[0028] Specifically, by setting to automatically download the compressed package of the corresponding required version file when the corresponding version file cannot be found in the local inventory, it avoids the possible delays and mistakes in the manual download operation process, and greatly improves the download efficiency.

[0029] In some embodiments, please refer to Figures 1 to 2 , the compressed package automatically synthesizes the corresponding download link through the url and is automatically downloaded into the alsa-utils folder.

[0030] Specifically, by setting the compressed package to automatically synthesize the corresponding download link through the url and automatically download it into the alsa-utils folder, it is realized that there is no need to manually splice or search for the download link, greatly improving the download efficiency and reducing the errors that may be brought by manual operations.

[0031] In some embodiments, please refer to Figures 1 to 2 , the downloaded compressed package is set to be automatically saved in the alsa-lib folder.

[0032] Specifically, the downloaded compressed package is set to be automatically saved in the alsa-lib folder, and the default setting is not to delete it, so that when it is necessary to use this version for compilation later, it can be directly read from the alsa-lib folder, avoiding the problem of slow compilation speed caused by repeated downloads, thereby achieving the effect of improving the compilation efficiency.

[0033] In some embodiments, it also includes the ability to read the user's local README.md file.

[0034] Specifically, the README.md file usually contains detailed documentation of the program. Adding the function of executing it in the program can allow users to conveniently obtain important information about the program, such as the purpose of the program, functional characteristics, usage methods, parameter descriptions, etc. By accessing the README.md file in the program, users do not need to search for documents in the external file system and can quickly find answers, reducing user confusion and usage barriers, thereby effectively improving user satisfaction with the program.

[0035] In some embodiments, the ALSA library includes a driver interface at the kernel level, libraries and tool sets in user space.

[0036] Specifically, the ALSA driver provides a unified interface for various sound cards, enabling upper-layer applications to not care about the details of the underlying hardware. The libraries in user space mainly include a series of functions and data structures for audio device management and control, providing API interfaces for user space application programs to call to communicate with audio devices. The tool set mainly includes aplay, arecord, amixer, etc. These tools are implemented by calling the APIs provided by ALSA-lib, providing users with convenient audio playback and recording functions.

[0037] In some embodiments, the embedded ALSA library constructed by the construction method is applicable to any one of the x86 architecture, ARM architecture, and MIPS architecture.

[0038] Specifically, the embedded ALSA library constructed by the construction method provided in this application can be applicable to any one of the x86 architecture, ARM architecture, and MIPS architecture, which means that users can select the corresponding adapted architecture according to the actual application scenario, indicating that the embedded ALSA library has high adaptability and practicality, and can provide a powerful and flexible solution for the audio processing of various embedded devices, thereby bringing a better audio experience and functional support to users.

[0039] Taking the x86 - arm cross - compiler using gcc7.5 as an example below, the operation process provided by the present invention will be introduced in detail. The specific flow chart is as Figure 3 shown: First, edit the proc.conf file and set the corresponding cross - compiler information and ALSA library version information. Specifically:

[0040]

[0041] Then set the version required by the alsa - lib library, whether to compile alsa - utils, and the required compilation platform options: Specifically:

[0042]

[0043] After setting the proc.conf configuration information, start executing the make command. Specifically, the Makefile will search whether there is an inventory of the required version in the alsa - lib folder and the alsa - utils folder. If the corresponding version can be found, it will be directly decompressed into the decode folder. If not, it will be automatically downloaded to these two folders and then decompressed into the decode folder. The decompressed files start to be compiled using the source code in the decode folder. The compiled result will be output to the out folder.

[0044] It should be noted that the library files and bin files in the out folder are all compiled files and can be moved to the target board for use. The downloaded compressed packages in the alsa - lib folder are not deleted by default, so that when compilation is required using this version later, it can be directly read from the alsa - lib folder, thereby achieving the purpose of avoiding the slowdown of the compilation speed caused by repeated downloads and effectively improving the compilation efficiency.

[0045] In subsequent use, since the cross - compiler file has been configured, options can be directly brought in when executing the make command for fast compilation:

[0046] make --platform=gcc7 --alsa - version=1.1.5 --alsa - utils=true

[0047] In some embodiments, the present application further provides an embedded target board, including a library directory and an embedded ALSA library, where the embedded ALSA library is constructed by the construction method in any of the above embodiments, and the embedded ALSA library is installed in the library directory.

[0048] In summary, for the embedded target board provided by the present invention, the library directory in the embedded target board installs the embedded ALSA library constructed by the construction method in any of the above embodiments, which can quickly manage a variety of cross-compilers, quickly implement the selection of different ALSA versions, and output the compilation results.

[0049] Obviously, those skilled in the art can make various changes and deformations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and deformations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application also intends to include these changes and deformations.

Claims

1. A method for constructing an embedded ALSA library, characterized in that, The construction method comprises the following steps: Step S1: Edit the proc.conf file and set corresponding configuration information, wherein the configuration information includes multiple cross-compiler version information, multiple required version files corresponding to alsa-lib folders, whether the alsa-utils library needs to be compiled, and the corresponding required compilation platform options; Step S2: Execute the make command to generate a Makefile file to search and check the alsa-lib folder and the alsa-utils folder, and determine whether the version file exists in the alsa-lib folder and the alsa-utils folder; Step S3: According to the determination result, the corresponding version file is decompressed into the Decode folder, and the source code in the Decode folder is used to compile and form a corresponding compiled file; Step S4: Output the compiled file to the out folder for storage.

2. The method for constructing an embedded ALSA library as claimed in claim 1, wherein: The step S4 also includes a step S41: when the determination result is that the corresponding version file does not exist in the alsa-utils folder, automatically downloading a compressed package corresponding to the version file.

3. The construction method of embedded ALSA library as claimed in claim 2, characterized in that, The compressed package is automatically downloaded to the alsa-utils folder by automatically synthesizing the corresponding download link through the url.

4. The method for constructing an embedded ALSA library as claimed in claim 3, wherein: The downloaded compressed package is set to be automatically saved in the alsa-lib folder.

5. The method for constructing an embedded ALSA library as described in any one of claims 1-4, characterized in that, The ALSA library includes a driver interface at the kernel level, a library and a tool set in the user space.

6. The method for constructing an embedded ALSA library as claimed in claim 5, wherein: The embedded ALSA library constructed by the construction method is suitable for any one of the x86 architecture, the ARM architecture and the MIPS architecture.

7. An embedded target board, characterized in that: include: A library directory and an embedded ALSA library, wherein the embedded ALSA library is constructed by the construction method according to any one of claims 1 to 6, and the embedded ALSA library is installed in the library directory.

Images