<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hi, I&#39;m Chris. on Krzysztof Bociurko (ChanibaL)</title>
    <link>https://chanibal.pl/</link>
    <description>Recent content in Hi, I&#39;m Chris. on Krzysztof Bociurko (ChanibaL)</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2022 Krzysztof Bociurko</copyright>
    <lastBuildDate>Tue, 11 Jan 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://chanibal.pl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Source code license</title>
      <link>https://chanibal.pl/license-code/</link>
      <pubDate>Tue, 11 Jan 2022 00:00:00 +0000</pubDate>
      
      <guid>https://chanibal.pl/license-code/</guid>
      <description>Copyright (c) 2022 Krzysztof Bociurko
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the &amp;ldquo;Software&amp;rdquo;), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:</description>
    </item>
    
    <item>
      <title>How to develop for ESP-IDF (ESP32) on VSCode Windows</title>
      <link>https://chanibal.pl/notes/esp32-vscode/</link>
      <pubDate>Tue, 31 Aug 2021 00:00:00 +0000</pubDate>
      
      <guid>https://chanibal.pl/notes/esp32-vscode/</guid>
      <description>ℹ️ Up to date as of 2021-08-31 with VSCode 1.59.1, Espressif IDF v1.1.1, Windows 10 64 Pro 64 bit 20H2, ESP-IDF 4.3.  A step by step tutorial on setting up Espressif&amp;rsquo;s IDE (the IDF) on Windows 10.
You can code in ESP-IDF in any IDEs. Personally I&amp;rsquo;ve used Visual Studio 2017 and 2019 with an always on terminal with IDF monitor for years. Recently Espressif released their own Visual Studio Code extension, I thought I&amp;rsquo;d give it a try.</description>
    </item>
    
    <item>
      <title>Visual Studio C&#43;&#43; NuGet issues with custom solution name</title>
      <link>https://chanibal.pl/notes/visual-studio-custom-solution-name-vs-nuget-cpp/</link>
      <pubDate>Fri, 06 Aug 2021 00:00:00 +0000</pubDate>
      
      <guid>https://chanibal.pl/notes/visual-studio-custom-solution-name-vs-nuget-cpp/</guid>
      <description>ℹ️ Dear googler (or equivalent), this is a bug-reportish rant.
There is no easy fix, but at least you might know this won&amp;rsquo;t work.  Setting custom solution name (changing from Release/Debug to something else) breaks NuGet.
Why? Look at the packages/{package name}/build file (this one comes from fmtlib):
&amp;lt;?xml version=&amp;#34;1.0&amp;#34; encoding=&amp;#34;utf-8&amp;#34;?&amp;gt; &amp;lt;Project ToolVersion=&amp;#34;4.0&amp;#34; xmlns=&amp;#34;http://schemas.microsoft.com/developer/msbuild/2003&amp;#34;&amp;gt; &amp;lt;!-- ... --&amp;gt; &amp;lt;ItemDefinitionGroup Condition=&amp;#34;&amp;#39;$(Configuration)&amp;#39;==&amp;#39;Debug&amp;#39;&amp;#34;&amp;gt; &amp;lt;Link&amp;gt; &amp;lt;AdditionalDependencies&amp;gt;fmtd.lib;%(AdditionalDependencies)&amp;lt;/AdditionalDependencies&amp;gt; &amp;lt;/Link&amp;gt; &amp;lt;Lib&amp;gt; &amp;lt;AdditionalDependencies&amp;gt;fmtd.lib;%(AdditionalDependencies)&amp;lt;/AdditionalDependencies&amp;gt; &amp;lt;/Lib&amp;gt; &amp;lt;/ItemDefinitionGroup&amp;gt; &amp;lt;ItemDefinitionGroup Condition=&amp;#34;&amp;#39;$(Configuration)&amp;#39;==&amp;#39;Release&amp;#39;&amp;#34;&amp;gt; &amp;lt;Link&amp;gt; &amp;lt;AdditionalDependencies&amp;gt;fmt.</description>
    </item>
    
  </channel>
</rss>
