<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>C&#43;&#43; on Spinicist</title>
    <link>https://www.spinicist.org.uk/tags/c&#43;&#43;/</link>
    <description>Recent content in C&#43;&#43; on Spinicist</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 14 Feb 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://www.spinicist.org.uk/tags/c++/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CMake and vcpkg My Way, Part 2</title>
      <link>https://www.spinicist.org.uk/posts/vcpkg-part2/</link>
      <pubDate>Sun, 14 Feb 2021 00:00:00 +0000</pubDate>
      
      <guid>https://www.spinicist.org.uk/posts/vcpkg-part2/</guid>
      <description>Question - How Do I Use Sanitizers with vcpkg?    In part 1 I gave a basic overview of using vcpkg in manifest mode. In this part I want to discuss how I integrated vcpkg into my CMake setup, which I haven&amp;rsquo;t seen elsewhere but I hope might be useful to others.
What led me to this particular setup was wanting to use Address Sanitizer across all my code.</description>
    </item>
    
    <item>
      <title>CMake and vcpkg My Way, Part 1</title>
      <link>https://www.spinicist.org.uk/posts/vcpkg-part1/</link>
      <pubDate>Sat, 13 Feb 2021 00:00:00 +0000</pubDate>
      
      <guid>https://www.spinicist.org.uk/posts/vcpkg-part1/</guid>
      <description>Intro    I&amp;rsquo;ve been meaning to start writing blog posts about developing scientific software with C++ for ages. What&amp;rsquo;s finally tipped me over the edge is being asked about how I use vcpkg on both the #includecpp and Eigen Discords. For these blog posts I&amp;rsquo;m aiming to keep a Question-Answer-Discussion format, because people seem to like brevity these days but I have deep tendency to rambling. However, I realised that in order to do this topic justice and stick to that format, I was going to have to split it into two parts.</description>
    </item>
    
  </channel>
</rss>
