Skip to content

Commit 150f5c5

Browse files
Create 2021-03-01-cpp-version.md (#14)
1 parent 76e169a commit 150f5c5

File tree

2 files changed

+15
-1
lines changed

2 files changed

+15
-1
lines changed

_posts/2021-01-13-usbguard-1.0.0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
layout: post
33
title: "New release: usbguard-1.0.0, and project enhancements!"
44
author: Radovan Sroka <rsroka@redhat.com>
5-
date: 2020-01-13 08:00:00+02:00
5+
date: 2021-01-13 08:00:00+02:00
66
tags: [usbguard, release notes, stable]
77
comments: false
88
---

_posts/2021-03-01-cpp-version.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
layout: post
3+
title: "Increasing compiler version to C++17"
4+
author: Zoltan Fridrich <zfridric@redhat.com>
5+
date: 2021-03-01 11:00:00+02:00
6+
comments: true
7+
sitemap:
8+
lastmod: 2021-03-01 11:00:00+02:00
9+
priority: 0.5
10+
changefreq: monthly
11+
exclude: 'no'
12+
---
13+
14+
As development packages are getting updated with latest features requiring newer versions of C++, we had to make a choice. We can either stuck with the old packages or start using new releases. After some investigation of newer C++ standards and its incompatibilities a decision has been made to increase the overall C++ version of USBGuard from C++11 to C++17. What does this mean for you? From now on, you will require a compiler that supports C++17 to be able to compile USBGuard sources. However, USBGuard will continue to work with old dependencies but will also support the newest development packages. An example of such package is [PEGTL](https://github.com/taocpp/PEGTL/releases/tag/3.2.0) of version 3 which uses C++17.

0 commit comments

Comments
 (0)