<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Zephyr: How to setup a build server using windows command line?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/111710/zephyr-how-to-setup-a-build-server-using-windows-command-line</link><description>Hi 
 We are developing Zephyr projects which are compiling and working fine with Visual Studio Code running on a Windows PC. 
 Now we want to build the projects on a build server running Windows. 
 The builds should be started from the command line. </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 31 May 2024 13:39:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/111710/zephyr-how-to-setup-a-build-server-using-windows-command-line" /><item><title>RE: Zephyr: How to setup a build server using windows command line?</title><link>https://devzone.nordicsemi.com/thread/486930?ContentTypeID=1</link><pubDate>Fri, 31 May 2024 13:39:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9719996f-6dbe-4aab-82db-e3bee79a555a</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;If you have installed the NCS versions using nRF Connect for Desktop -&amp;gt; Toolchain Manager, it is possible to use this to generate environment scripts:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/4186.pastedimage1717162579612v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;I use these to change between NCS versions.&lt;/p&gt;
&lt;p&gt;Just put them somewhere in the path of Windows, and rename them to reflect the NCS version that they represent. Then you can just call them from any terminal, and it will set up the environment for that NCS version.&lt;/p&gt;
&lt;p&gt;In case you are not using nRF Connect for Desktop -&amp;gt; Toolchain Manager, just test this on a different computer, and have a look at the generated environment file. It should be pretty easy to replicate this manually for your build server.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>