forked from pool/cmake
Dirk Mueller
93d7df6bb1
* The “ASM_MARMASM” language was added to support the Microsoft ARM assembler language. * CMake now writes a YAML log of configure-time checks to “CMakeFiles/CMakeConfigureLog.yaml” under the top of the build tree. * The “cmake-file-api(7)” “codemodel” version 2 “target” object gained a new “fileSets” field and associated “fileSetIndex” field to “sources” objects. OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/cmake?expand=0&rev=517 |
||
---|---|---|
_constraints | ||
_multibuild | ||
.gitattributes | ||
.gitignore | ||
cmake-3.26.0-SHA-256.txt | ||
cmake-3.26.0-SHA-256.txt.asc | ||
cmake-3.26.0.tar.gz | ||
cmake-fix-png-include-dir.patch | ||
cmake-fix-ruby-test.patch | ||
cmake.attr | ||
cmake.changes | ||
cmake.keyring | ||
cmake.macros | ||
cmake.prov | ||
cmake.spec | ||
feature-suse-python-interp-search-order.patch | ||
glibc-236.patch | ||
README.SUSE |
The package 'cmake' only ships a README.SUSE file and serves as a meta-package. cmake requires cmake-implementation, which inside OBS is provided by * cmake-mini (minimal cmake variant, no especially no libcurl/libarchive) * cmake-full (what used to be called cmake before) This complex setup was done in order to be able to eliminate build cycles, as more and more tools were moving to cmake as build system, but with curl in the build chain, was making it increasingly difficult to break the cycle. cmake-mini is not meant for installation on end-user systems (where it also would not save a lot; as an end user, you have libcurl on your system anyway due to libzypp) and is thus not part of the FTP Tree.