<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Build Time Checks on The Lone C++ Coder's Blog</title><link>https://www.lonecpluspluscoder.com/tags/build-time-checks/</link><description>Recent content in Build Time Checks on The Lone C++ Coder's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 05 Dec 2014 07:00:18 +0000</lastBuildDate><atom:link href="https://www.lonecpluspluscoder.com/tags/build-time-checks/index.xml" rel="self" type="application/rss+xml"/><item><title>Checking C++ library versions during build time</title><link>https://www.lonecpluspluscoder.com/2014/12/05/checking-c-library-versions-build-time/</link><pubDate>Fri, 05 Dec 2014 07:00:18 +0000</pubDate><author>Timo Geusch</author><guid>https://www.lonecpluspluscoder.com/2014/12/05/checking-c-library-versions-build-time/</guid><description>&lt;p>In my previous post, I discussed &lt;a href="https://www.lonecpluspluscoder.com/2014/12/03/managing-third-party-libraries-c-projects/" title="Managing third party libraries in C&amp;#43;&amp;#43; projects">various strategies for managing third party libraries&lt;/a>. In this post I&amp;rsquo;ll discuss a couple of techniques you can use to ensure that a specific version of your source code will get compiled with the correct version of the required libraries.&lt;/p>
&lt;p>Yes, you can rely on your package management tools to always deliver you the correct versions. If you&amp;rsquo;re a little more paranoid and/or spent way too much time debugging problems stemming from mixing the wrong libraries, you may want to continue reading.&lt;/p></description></item></channel></rss>