<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>C++ on Dr. Eric T. Dawson</title><link>http://www.erictdawson.com/series/c++/</link><description>Recent content in C++ on Dr. Eric T. Dawson</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 04 Nov 2015 00:00:00 +0000</lastBuildDate><atom:link href="http://www.erictdawson.com/series/c++/index.xml" rel="self" type="application/rss+xml"/><item><title>Organizing compilable projects</title><link>http://www.erictdawson.com/posts/organizing-compilable-projects/</link><pubDate>Wed, 04 Nov 2015 00:00:00 +0000</pubDate><guid>http://www.erictdawson.com/posts/organizing-compilable-projects/</guid><description>&lt;pre tabindex="0">&lt;code> package_name
 README.md
 Makefile AND/OR configure AND/OR install.sh
 |___bin
 |___lib
 |___include
 |___src
 |___doc
 |___test
&lt;/code>&lt;/pre>&lt;p>I&amp;rsquo;ve been wrangling a new-to-me C++ project over the past few weeks, and I&amp;rsquo;ve realized that it is by no means the first bioinformatics package to use a non-canonical build format. I don&amp;rsquo;t mean to pick on the field. Science will always come first, but there are good reasons for following solid design practices even if it&amp;rsquo;s just a small piece of code for in-house use. You never know if a piece of code will become important enough to publish at a later date.&lt;/p></description></item></channel></rss>