Search results
Results From The WOW.Com Content Network
pkg-config is software development tool that queries information about libraries from a local, file-based database for the purpose of building a codebase that depends on them. . It allows for sharing a codebase in a cross-platform way by using host-specific library information that is stored outside of yet referenced by the codeba
First, native build tool configuration files are generated from CMake configuration files – written in the CMake scripting language. The command line syntax is cmake <dir> where <dir> is a directory that contains a CMakeLists.txt file.
Called meta-build tools, these generate configuration files for other build tools such as those listed above. CMake – Cross-platform build tool for configuring platform-specific builds; very popoular; integrated with IDEs such as Qt Creator, [1] KDevelop and GNOME Builder [2]
Meson can automatically find and use external dependencies installed on the users system via pkg-config, CMake, and project-specific lookups. [18] Alternatively, or as a fallback, a dependency can be provided as a subproject – a Meson project within another, either contained or as a download link, possibly with patches. [ 19 ]
Existing tools such as Make can be used via custom configuration file or command-line parameters. Custom tools such as shell scripts can also be used. Some tools, such as shell scripts, are task-oriented declarative programming. They encode sequences of commands to perform with usually minimal conditional logic.
A software build is the process of converting source code files into standalone software artifact(s) that can be run on a computer, or the result of doing so. [1]In software production, builds optimize software for performance and distribution, packaging into formats such as '.exe'; '.deb'; '.apk'.
The predecessor tool is a question-and-answer-based utility (make config, make oldconfig). Variations of the tool for Linux configuration include: make xconfig, which requires Qt; make gconfig, which uses GTK+; make nconfig, which is similar to make menuconfig. All these tools use the Kconfig language internally.
If a .in file has changed then it suffices to re-run config.status and make. If the body of source code is copied to another computer then it is sufficient to re-run configure (which runs config.status) and make. (For this reason source code using Autotools is normally distributed without the files that configure generates.)