<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Programming on toeb / notes</title><link>https://toeb.github.io/categories/programming/</link><description>Recent content in Programming on toeb / notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 27 Nov 2014 00:00:00 +0000</lastBuildDate><atom:link href="https://toeb.github.io/categories/programming/index.xml" rel="self" type="application/rss+xml"/><item><title>CMake and the Filesystem</title><link>https://toeb.github.io/post/cmakeppfilesystem/</link><pubDate>Thu, 27 Nov 2014 00:00:00 +0000</pubDate><guid>https://toeb.github.io/post/cmakeppfilesystem/</guid><description>&lt;h1 id="filesystem"&gt;Filesystem&lt;/h1&gt;&#10;&lt;p&gt;I have always been a bit confused when working with cmake’s file functions and the logic behind paths (sometimes they are found sometimes they are not…) For ease of use I reimplemented a own path managing system which behaves very similar to powershell and bash (see ss64.com) it is based around a global path stack and path qualification. All of my functions which work with paths use this system.&lt;/p&gt;</description></item></channel></rss>