PKGBUILDs | creating various Arch Linux packages ( including lots
kandi X-RAY | PKGBUILDs Summary
kandi X-RAY | PKGBUILDs Summary
PKGBUILDs is a Shell library. PKGBUILDs has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.
PKGBUILDs for creating various Arch Linux packages (including lots of mingw-w64 cross compiler packages)
PKGBUILDs for creating various Arch Linux packages (including lots of mingw-w64 cross compiler packages)
Support
Quality
Security
License
Reuse
Support
PKGBUILDs has a low active ecosystem.
It has 99 star(s) with 43 fork(s). There are 9 watchers for this library.
It had no major release in the last 6 months.
There are 3 open issues and 101 have been closed. On average issues are closed in 329 days. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of PKGBUILDs is current.
Quality
PKGBUILDs has no bugs reported.
Security
PKGBUILDs has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
PKGBUILDs is licensed under the GPL-2.0 License. This license is Strong Copyleft.
Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.
Reuse
PKGBUILDs releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of PKGBUILDs
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of PKGBUILDs
PKGBUILDs Key Features
No Key Features are available at this moment for PKGBUILDs.
PKGBUILDs Examples and Code Snippets
No Code Snippets are available at this moment for PKGBUILDs.
Community Discussions
No Community Discussions are available at this moment for PKGBUILDs.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install PKGBUILDs
Currently, I test with qmake and CMake. With both build systems it is possible to use either the shared or the static libraries. Please read the comments in the PKGBUILD file itself and the pinned comments in the AUR for futher information. There are also pkg-config files, but those aren't really tested. qbs and windeployqt currently don't work very well (see issues). Using the static libraries or mxedeployqt might be an alternative for windeployqt.
In order to build a Qt-based project using mingw-w64-qt6 packages one also needs to install the regular qt6-base package for development tools such as moc. The packages qt6-tools and qt6-declarative contain also native packages which might be required by some projects. Currently, I test only CMake. It is possible to use either the shared or the static libraries. The static libraries are installed into a nested prefix (/usr/i686-w64-mingw32/static and /usr/x86_64-w64-mingw32/static) so this prefix needs to be prepended to CMAKE_FIND_ROOT_PATH for using the static libraries. To generally prefer static libraries one might use the helper scripts provided by the mingw-w64-cmake-static package. The build systems qbs and qmake are not tested. It looks like Qt's build system does not install pkg-config files anymore and so far no effort has been taken to enable them. Note that windeployqt needed to be enabled by the official/regular qt6-tools package but would likely not work very well anyways. Using the static libraries or mxdeployqt might be an alternative for windeployqt.
In order to build a Qt-based project using mingw-w64-qt6 packages one also needs to install the regular qt6-base package for development tools such as moc. The packages qt6-tools and qt6-declarative contain also native packages which might be required by some projects. Currently, I test only CMake. It is possible to use either the shared or the static libraries. The static libraries are installed into a nested prefix (/usr/i686-w64-mingw32/static and /usr/x86_64-w64-mingw32/static) so this prefix needs to be prepended to CMAKE_FIND_ROOT_PATH for using the static libraries. To generally prefer static libraries one might use the helper scripts provided by the mingw-w64-cmake-static package. The build systems qbs and qmake are not tested. It looks like Qt's build system does not install pkg-config files anymore and so far no effort has been taken to enable them. Note that windeployqt needed to be enabled by the official/regular qt6-tools package but would likely not work very well anyways. Using the static libraries or mxdeployqt might be an alternative for windeployqt.
Support
SyntaxHelperUtilities
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page