From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 1/3] cmake: Update to 3.14.5
Date: Thu, 04 Jul 2019 14:23:10 +0200 [thread overview]
Message-ID: <20190704122312.9655-1-stefan.schantl@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]
This is a minor update to the latest stable version of cmake.
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
---
cmake/cmake.nm | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/cmake/cmake.nm b/cmake/cmake.nm
index 8bb3a3c63..ee8e91015 100644
--- a/cmake/cmake.nm
+++ b/cmake/cmake.nm
@@ -6,7 +6,7 @@
name = cmake
version = %{ver_maj}.%{ver_min}
ver_maj = 3.14
-ver_min = 1
+ver_min = 5
release = 1
groups = Development/Tools
@@ -15,11 +15,11 @@ license = BSD
summary = Cross-platform make system.
description
- CMake is used to control the software compilation process using simple \
- platform and compiler independent configuration files. CMake generates \
- native makefiles and workspaces that can be used in the compiler \
- environment of your choice. CMake is quite sophisticated: it is possible \
- to support complex environments requiring system configuration, pre-processor \
+ CMake is used to control the software compilation process using simple
+ platform and compiler independent configuration files. CMake generates
+ native makefiles and workspaces that can be used in the compiler
+ environment of your choice. CMake is quite sophisticated: it is possible
+ to support complex environments requiring system configuration, pre-processor
generation, code generation, and template instantiation.
end
--
2.21.0
next reply other threads:[~2019-07-04 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 12:23 Stefan Schantl [this message]
2019-07-04 12:23 ` [PATCH 2/3] libedit: Update to 3.1-20190324 Stefan Schantl
2019-07-04 12:23 ` [PATCH 3/3] llvm: New package Stefan Schantl
2019-07-04 15:01 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190704122312.9655-1-stefan.schantl@ipfire.org \
--to=stefan.schantl@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox