<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gulrak.net</title>
    <link>https://gulrak.net/</link>
    <description>Recent content on Gulrak.net</description>
    <generator>Hugo -- gohugo.io</generator>
    <copyright>(C) 1999-2023 by Steffen Schümann, Hamburg</copyright>
    <lastBuildDate>Sun, 27 Dec 2020 11:38:44 +0200</lastBuildDate><atom:link href="https://gulrak.net/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ghc::filesystem Release v1.3.10</title>
      <link>https://gulrak.net/posts/2020-std-filesystem-release-v1-3-10/</link>
      <pubDate>Sun, 27 Dec 2020 11:38:44 +0200</pubDate>
      
      <guid>https://gulrak.net/posts/2020-std-filesystem-release-v1-3-10/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
Today I released [v1.3.10](https://github.com/gulrak/filesystem/releases/tag/v1.3.10) of
[`ghc::filesystem`](https://github.com/gulrak/filesystem), my implementation of C++17
[`std::filesystem`](https://en.cppreference.com/w/cpp/filesystem) for C++11, C++14 and C++17.
&lt;p&gt;This Release small release fixes the missing &lt;code&gt;constexpr&lt;/code&gt; of bitmask operations an issue where
&lt;code&gt;Source&lt;/code&gt; template parameters where not allowed to be used with &lt;code&gt;std::string_view&lt;/code&gt; when using C++17.&lt;/p&gt;
&lt;p&gt;I expect this to be the last v1.3.x release, as my focus is now getting the C++20 support done
and releasing it with v1.4.0.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>ghc::filesystem Release v1.3.8</title>
      <link>https://gulrak.net/posts/2020-std-filesystem-release-v1-3-8/</link>
      <pubDate>Sun, 15 Nov 2020 20:56:12 +0200</pubDate>
      
      <guid>https://gulrak.net/posts/2020-std-filesystem-release-v1-3-8/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
Today I released [v1.3.8](https://github.com/gulrak/filesystem/releases/tag/v1.3.8) of
[`ghc::filesystem`](https://github.com/gulrak/filesystem), my implementation of C++17
[`std::filesystem`](https://en.cppreference.com/w/cpp/filesystem) for C++11, C++14 and C++17.
&lt;p&gt;This Release mainly fixes an issue with reparse points under windows and the &lt;code&gt;skip_permission_denied&lt;/code&gt;
handling on directory iteration.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>ghc::filesystem Release v1.3.6</title>
      <link>https://gulrak.net/posts/2020-std-filesystem-release-v1-3-6/</link>
      <pubDate>Sat, 10 Oct 2020 07:46:12 +0200</pubDate>
      
      <guid>https://gulrak.net/posts/2020-std-filesystem-release-v1-3-6/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
Today I released [v1.3.6](https://github.com/gulrak/filesystem/releases/tag/v1.3.6) of
[`ghc::filesystem`](https://github.com/gulrak/filesystem), my implementation of C++17
[`std::filesystem`](https://en.cppreference.com/w/cpp/filesystem) for C++11, C++14 and C++17.
&lt;p&gt;This Release adds CentOS 7 and 8 to the CI tested and supported platforms. Additionally
the &lt;code&gt;fs::path&lt;/code&gt; class was optimized to create less copies and temporaries during many
operations.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>ghc::filesystem Release v1.3.4</title>
      <link>https://gulrak.net/posts/2020-std-filesystem-release-v1-3-4/</link>
      <pubDate>Sun, 30 Aug 2020 08:03:34 +0200</pubDate>
      
      <guid>https://gulrak.net/posts/2020-std-filesystem-release-v1-3-4/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
Today I released [v1.3.4](https://github.com/gulrak/filesystem/releases/tag/v1.3.4) of
[`ghc::filesystem`](https://github.com/gulrak/filesystem), my implementation of C++17
[`std::filesystem`](https://en.cppreference.com/w/cpp/filesystem) for C++11, C++14 and C++17.
&lt;p&gt;This Release added some enhancements to better support Android and Emscripten.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>ghc::filesystem Release v1.3.2</title>
      <link>https://gulrak.net/posts/2020-std-filesystem-release-v1-3-2/</link>
      <pubDate>Mon, 30 Mar 2020 22:54:30 +0200</pubDate>
      
      <guid>https://gulrak.net/posts/2020-std-filesystem-release-v1-3-2/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
Today I released [v1.3.2](https://github.com/gulrak/filesystem/releases/tag/v1.3.2) of
[`ghc::filesystem`](https://github.com/gulrak/filesystem), my implementation of C++17
[`std::filesystem`](https://en.cppreference.com/w/cpp/filesystem) for C++11, C++14 and C++17.
&lt;p&gt;This Release added CI support for FreeBSD and ARM Linux, thanks to generous
support with pull requests from &lt;em&gt;nightlark&lt;/em&gt;, and some bug fixes. The two new
platforms are possible with the service of &lt;em&gt;Cirrus CI&lt;/em&gt; and &lt;em&gt;Drone&lt;/em&gt;.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>std::filesystem Implementation Corner Cases, part 2</title>
      <link>https://gulrak.net/posts/2020-std-filesystem-corner-cases-2/</link>
      <pubDate>Sat, 08 Feb 2020 23:30:19 +0100</pubDate>
      
      <guid>https://gulrak.net/posts/2020-std-filesystem-corner-cases-2/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
A [question on StackOverflow](https://stackoverflow.com/questions/60130796/return-value-of-stdfilesystemcreate-directories-on-paths-with-trailing-sla)
was pointing at another corner case where the current implementations of
std::filesystem differ, it is about the handling of a trailing directory
seperator when calling `std::filesystem::create_directories()`.</description>
    </item>
    
    <item>
      <title>ghc::filesystem Release v1.3.0</title>
      <link>https://gulrak.net/posts/2020-ghc-filesystem-release-v1-3-0/</link>
      <pubDate>Sat, 08 Feb 2020 19:30:35 +0100</pubDate>
      
      <guid>https://gulrak.net/posts/2020-ghc-filesystem-release-v1-3-0/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
Today I released [v1.3.0](https://github.com/gulrak/filesystem/releases/tag/v1.3.0) of
[`ghc::filesystem`](https://github.com/gulrak/filesystem), my implementation of C++17
[`std::filesystem`](https://en.cppreference.com/w/cpp/filesystem) for C++11, C++14 and C++17.
&lt;p&gt;The main reasong for this release is the switch from BSD-3-Clause license to the MIT license.&lt;/p&gt;
&lt;p&gt;I originally decided on BSD because of the detailed clauses it features, to make things clear,
but it was not an easy decision at that time, but I had to pick one.&lt;/p&gt;
&lt;p&gt;About a week ago I was asked if it would be possible to use MIT license and at first I was
against a change, but I thought about it and decided a even ore liberal license would
give more projects the chance to use it, so my only concern left was, if I would be able
to reach all contributors and if they would agree to the license change.&lt;/p&gt;
&lt;p&gt;I was amazed to see, all anserwed in just a few days and all agreed so they made the
decision an easy one for me.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>std::filesystem Implementation Corner Cases</title>
      <link>https://gulrak.net/posts/2019-std-filesystem-corner-cases/</link>
      <pubDate>Sun, 22 Dec 2019 13:24:31 +0100</pubDate>
      
      <guid>https://gulrak.net/posts/2019-std-filesystem-corner-cases/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
On this years [Meeting C++](https://meetingcpp.com/2019/) I had the chance to talk
with a lot of people and it was very inspirational. With some I talked about
[ghc::filesystem](https://github.com/gulrak/filesystem), my implementation of a
C++17 `std::filesystem` compatible library. Part of this discussions was about
some corner cases I found during my tests, and I was trying to remember the
details when I was having the chance to talk to [@NicoJosuttis](https://twitter.com/NicoJosuttis).
He among others was interested in these issues, as they might be rooted in unclear passages of the standard.</description>
    </item>
    
    <item>
      <title>ghc::filesystem Release v1.2.10</title>
      <link>https://gulrak.net/posts/2019-ghc-filesystem-release-v1-2-10/</link>
      <pubDate>Sun, 24 Nov 2019 16:42:51 +0100</pubDate>
      
      <guid>https://gulrak.net/posts/2019-ghc-filesystem-release-v1-2-10/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
Today I released the bugfix release [v1.2.10](https://github.com/gulrak/filesystem/releases/tag/v1.2.10) of [`ghc::filesystem`](https://github.com/gulrak/filesystem), my implementation of C++17 [`std::filesystem`](https://en.cppreference.com/w/cpp/filesystem) for
C++11, C++14 and C++17. There were some issues, all on the Windows part, so it was time to fix them with 
a release.
&lt;p&gt;While at it, I updated the CI configuration files to add newer compilers and the set used for CI and tests
is now:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;macOS 10.12: Xcode 9.2 (clang-900.0.39.2), GCC 9.2, Clang 9.0, macOS 10.13: Xcode 10.1, macOS 10.14: Xcode 11.2&lt;/li&gt;
&lt;li&gt;Windows: Visual Studio 2017, Visual Studio 2015, Visual Studio 2019, MinGW GCC 6.3 (Win32), GCC 7.2 (Win64)&lt;/li&gt;
&lt;li&gt;Linux (Ubuntu): GCC (5.5, 6.5, 7.4, 8.3, 9.2), Clang (5.0, 6.0, 7.1, 8.0, 9.0)&lt;/li&gt;
&lt;/ul&gt;</description>
    </item>
    
    <item>
      <title>ghc::filesystem Release v1.2.8</title>
      <link>https://gulrak.net/posts/2019-ghc-filesystem-release-v1-2-8/</link>
      <pubDate>Fri, 15 Nov 2019 09:10:03 +0200</pubDate>
      
      <guid>https://gulrak.net/posts/2019-ghc-filesystem-release-v1-2-8/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
During these days I&#39;m on the [Meeting C++ 2019](https://meetingcpp.com/2019/) and so far it is a great event. This morning before leaving my hotel, I used the inspirational spirit and released v1.2.8 of [`ghc::filesystem`](https://github.com/gulrak/filesystem). This is mostly a bugfix release, but there is a new CMake option to select wether or
not an install target should be added to the build files.
&lt;p&gt;Additionally, five pull requests found their way into this release, and I want to thank the supporters for their work.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>ghc::filesystem Release v1.2.6</title>
      <link>https://gulrak.net/posts/2019-ghc-filesystem-release-v1-2-6/</link>
      <pubDate>Sat, 21 Sep 2019 17:45:08 +0200</pubDate>
      
      <guid>https://gulrak.net/posts/2019-ghc-filesystem-release-v1-2-6/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
Today I released v1.2.6 of [`ghc::filesystem`](https://github.com/gulrak/filesystem). The main reason was an
issue with `fs::path::preferred_seperator`. The previous implementation didn&#39;t compile on pre-C++17 compilers when the seperator was accessed. The Bugfix for [#27](https://github.com/gulrak/filesystem/issue/27), was a bit more work than expected, but now it works on all tested compilers.
&lt;p&gt;Additionally, two pull requests found their way into this release, and I want to thank the supporters for their work.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Work on reLive Continued</title>
      <link>https://gulrak.net/posts/2019-work-on-relive-continued/</link>
      <pubDate>Sun, 15 Sep 2019 01:36:38 +0200</pubDate>
      
      <guid>https://gulrak.net/posts/2019-work-on-relive-continued/</guid>
      <description>&lt;p&gt;With the initial release of a working prototype of a new reLive streaming client I started to
work on reLive again. The first result is a curses based console application for macOS and
Linux. It is still a bit rough around the edges, but it fetches all metadata, has a database
backend and plays shows.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://raw.githubusercontent.com/gulrak/relive-client/master/screenshots/relivecui-linux-streams_v0.3.33.png&#34; alt=&#34;reLiveCUI&#34;&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>ghc::filesystem Release v1.2.4</title>
      <link>https://gulrak.net/posts/2019-ghc-filesystem-release-v1-2-4/</link>
      <pubDate>Sun, 11 Aug 2019 10:21:07 +0200</pubDate>
      
      <guid>https://gulrak.net/posts/2019-ghc-filesystem-release-v1-2-4/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
Today I released v1.2.4 of [`ghc::filesystem`](https://github.com/gulrak/filesystem).
It mainly contains a fix for issue [#22](https://github.com/gulrak/filesystem/pull/22),
where `ghc::filesystem::copy()` wouldn&#39;t allways forward given `copy_options` to
a `ghc::filesystem::copy_file()` call.</description>
    </item>
    
    <item>
      <title>Moved to a new server again.</title>
      <link>https://gulrak.net/posts/2019-new-server/</link>
      <pubDate>Sat, 10 Aug 2019 17:25:42 +0200</pubDate>
      
      <guid>https://gulrak.net/posts/2019-new-server/</guid>
      <description>&lt;p&gt;&lt;span class=&#34;glyphicon glyphicon-hdd&#34; aria-hidden=&#34;true&#34; style=&#34;margin: 4px 0 4px 10px; font-size: 3.5em; float: right;&#34;&gt;&lt;/span&gt;
My previous server, based on Intel&amp;rsquo;s 8-Core-Atom C2750, was handling my mails,
domains and repositories for about five years. Most of the time, I was quite
happy with the system, but still, time passes and hardware ages fast.
When last month the system dropped offline and was unreachable even through
the remote serial connection, I was kind of shocked even with a relativly
recent backup.&lt;/p&gt;
&lt;p&gt;I called my hosting provider IONOS, and they where kind enough to find the issue
(a dead mainboard) and replace the system, keeping my RAID1 HDDs, and getting
everything up and running again in about an hour, and that on a sunday night.
So thank you to all the unnamed service technicians that where involved in this!&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Impressum - Legal Notice</title>
      <link>https://gulrak.net/legal/</link>
      <pubDate>Sat, 10 Aug 2019 17:10:05 +0200</pubDate>
      
      <guid>https://gulrak.net/legal/</guid>
      <description>Gulrak.de/Gulrak.net is a private, non-commercial site made by:
Steffen Schümann
Störtebekerweg 48a
21149 Hamburg
Germany
Phone: +49 171 9546137
For problems concerning the site, you can also contact: webmaster@gulrak.de
Disclaimer Limitation of liability for internal content The content of our website has been compiled with meticulous care and to the best of our knowledge. However, we cannot assume any liability for the up-to-dateness, completeness or accuracy of any of the pages.</description>
    </item>
    
    <item>
      <title>Privacy Policy</title>
      <link>https://gulrak.net/privacy/</link>
      <pubDate>Sat, 10 Aug 2019 17:09:59 +0200</pubDate>
      
      <guid>https://gulrak.net/privacy/</guid>
      <description>Personal data (usually referred to just as &amp;ldquo;data&amp;rdquo; below) will only be processed by us to the extent necessary and for the purpose of providing a functional and user-friendly website, including its contents, and the services offered there.
Per Art. 4 No. 1 of Regulation (EU) 2016/679, i.e. the General Data Protection Regulation (hereinafter referred to as the &amp;ldquo;GDPR&amp;rdquo;), &amp;ldquo;processing&amp;rdquo; refers to any operation or set of operations such as collection, recording, organization, structuring, storage, adaptation, alteration, retrieval, consultation, use, disclosure by transmission, dissemination, or otherwise making available, alignment, or combination, restriction, erasure, or destruction performed on personal data, whether by automated means or not.</description>
    </item>
    
    <item>
      <title>Projects</title>
      <link>https://gulrak.net/projects/</link>
      <pubDate>Sat, 10 Aug 2019 14:20:52 +0200</pubDate>
      
      <guid>https://gulrak.net/projects/</guid>
      <description>In my spare time, I like to code for fun, for trying out new stuff to learn new things and sometimes to solve a problem I have. Most of the projects will never reach the public, but sometimes, the result is usefull for others.
Information on these can be found here:
ghc::filesystem on GitHub An implementation of std::filesystem from C++17, based on features of C++11, so usable for any at least C++11 compatible compiler on Linux, macOS and Windows.</description>
    </item>
    
    <item>
      <title>ghc::filesystem Release v1.2.2</title>
      <link>https://gulrak.net/posts/2019-ghc-filesystem-release-v1-2-2/</link>
      <pubDate>Sun, 23 Jun 2019 16:50:38 +0200</pubDate>
      
      <guid>https://gulrak.net/posts/2019-ghc-filesystem-release-v1-2-2/</guid>
      <description>&lt;img style=&#34;margin: 4px 0 4px 10px; width: 64px; height: 64px; float: right;&#34; src=&#34;https://gulrak.net/img/cpp_logo.png&#34;&gt;
Today I released a bugfix version of [`ghc::filesystem`](https://github.com/gulrak/filesystem).
It only contains a fix for issue [#21](https://github.com/gulrak/filesystem/pull/21),
where compiling on Alpine Linux with `musl` instead of `glibc` chooses the wrong `strerror_r`
signature.
&lt;p&gt;The &lt;code&gt;musl&lt;/code&gt; headers sadly don&amp;rsquo;t conform to the preprocessor expression of the linux man
file &lt;code&gt;(_POSIX_C_SOURCE &amp;gt;= 200112L || _XOPEN_SOURCE &amp;gt;= 600) &amp;amp;&amp;amp; ! _GNU_SOURCE&lt;/code&gt;
for &lt;code&gt;strerror_r&lt;/code&gt;, so there was no well defined preprocessor way of solving this.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Revision 2019 - Party Fazit</title>
      <link>https://gulrak.net/posts/2019-revision-party-fazit/</link>
      <pubDate>Tue, 23 Apr 2019 22:15:20 +0200</pubDate>
      
      <guid>https://gulrak.net/posts/2019-revision-party-fazit/</guid>
      <description>Nun sind wir zurück von der Revision 2019 und auch wenn der Abbau etwas stressiger, und ich nicht immer ganz fit war: Die Party war großartig und die Produktionen haben mich wieder begeistert!
Jedes Jahr bin ich überrascht, wie schnell die vier Party-Tage vorbeirasen. Ja, eine Infodesk-Schicht im Morgengrauen kann etwas weniger rasant sein, aber wenn es Montag ist geht alles so schnell, und eh man sich versieht ist die Halle von den Scenern geräumt, und wartet auf Abbau und durchfegen.</description>
    </item>
    
  </channel>
</rss>
