<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Testing changes]]></title><description><![CDATA[<p dir="auto">I'm getting an itch to tinker with the HISE source code but being unfamiliar with working on projects of this scale I have a very basic question. If I make a change how do I test it, or to be more exact do I have to recompile/rebuild the whole project every time I want to test a change (no matter how small)?</p>
]]></description><link>https://forum.hise.audio/topic/637/testing-changes</link><generator>RSS for Node</generator><lastBuildDate>Fri, 14 Aug 2026 08:58:27 GMT</lastBuildDate><atom:link href="https://forum.hise.audio/topic/637.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 25 Mar 2018 10:23:37 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Testing changes on Sun, 25 Mar 2018 10:37:54 GMT]]></title><description><![CDATA[<p dir="auto">Yes, but the compiler is smart and only rebuilds the files that you've changed (however if you change a file that is used by other files they will also be recompiled). It won't be as fast as compiling scripts though - otherwise the whole scripting engine would be pointless ;)</p>
<p dir="auto">If you're on Linux, try to use VS Code with the C++ extension, this gives the best UX IMHO.</p>
]]></description><link>https://forum.hise.audio/post/3983</link><guid isPermaLink="true">https://forum.hise.audio/post/3983</guid><dc:creator><![CDATA[Christoph Hart]]></dc:creator><pubDate>Sun, 25 Mar 2018 10:37:54 GMT</pubDate></item></channel></rss>