<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vcpkg on Matt Bolitho</title><link>https://mattbolitho.github.io/tags/vcpkg/</link><description>Recent content in Vcpkg on Matt Bolitho</description><generator>Hugo -- gohugo.io</generator><language>en-GB</language><copyright>Matt Bolitho</copyright><lastBuildDate>Wed, 17 Apr 2024 08:00:00 +0000</lastBuildDate><atom:link href="https://mattbolitho.github.io/tags/vcpkg/index.xml" rel="self" type="application/rss+xml"/><item><title>vcpkg with libc++</title><link>https://mattbolitho.github.io/posts/vcpkg-with-libcxx/</link><pubDate>Wed, 17 Apr 2024 08:00:00 +0000</pubDate><guid>https://mattbolitho.github.io/posts/vcpkg-with-libcxx/</guid><description>I have been using vcpkg for a few C++ projects recently. Over the last few months or so, I have mostly been switching over to LLVM tools for my personal C++ projects.
One small pain point is that, if you link against libc++ with your consuming project that links against libraries from vcpkg, you will almost certainly get linker errors. This is because vcpkg will link libraries against libstdc++ by default and, because your project uses libc++ instead, you will get undefined symbols.</description></item></channel></rss>