<?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>Can not install toolchain for 3rd party SDK (ie stock zephyr)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/126521/can-not-install-toolchain-for-3rd-party-sdk-ie-stock-zephyr</link><description>Development environment: MacOS Sequoia (15.4.1), Visual Studio Code v1.108 0, nrfConnect 2026.1.1242 
 I am trying to develop a &amp;quot;workspace&amp;quot; project with a nRF52840DK as my development target using the nrf-connect vs-code extension. I am unable to figure</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 28 Jan 2026 09:00:39 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/126521/can-not-install-toolchain-for-3rd-party-sdk-ie-stock-zephyr" /><item><title>RE: Can not install toolchain for 3rd party SDK (ie stock zephyr)</title><link>https://devzone.nordicsemi.com/thread/559755?ContentTypeID=1</link><pubDate>Wed, 28 Jan 2026 09:00:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0191d7ce-f4b2-4672-aaa1-01e167532d09</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi Kent,&lt;/p&gt;
&lt;p&gt;No problem. Looking back I can see that my answer may have sounded more like a workaround than a proper solution. What’s happening is that before looking for installed Zephyr SDKs in the CMake package registry, the extension checks if&amp;nbsp;build tools such as west are available on PATH. Only if they are found will the installed/registered Zephyr SDK(s) be displayed. (NCS toolchains don’t require this check since they bundle the build tools.) Another solution is&amp;nbsp;update your PATH in ~/.zshrc to include the path to where you your &amp;#39;west&amp;#39; executable is located. Then you won’t need to launch VS Code from the terminal to inherit a working build environment.&lt;/p&gt;
[quote user="kent@khauser.net"]If you can confirm that the stock toolchains must be installed outside of the GUI and can not be selected except via the method you have identified[/quote]
&lt;p&gt;Correct, the GUI only supports installation of NCS toolchains.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not install toolchain for 3rd party SDK (ie stock zephyr)</title><link>https://devzone.nordicsemi.com/thread/559735?ContentTypeID=1</link><pubDate>Wed, 28 Jan 2026 01:28:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:04bec8d5-bc59-4a2a-a2db-8838520b9915</guid><dc:creator>kent96822</dc:creator><description>&lt;p&gt;Hi Vidar.&lt;/p&gt;
&lt;p&gt;Sorry I took so long to get back you. I Didn&amp;#39;t realize you were nordic support &amp;amp; just thought it was another user suggesting a work-around.&lt;/p&gt;
&lt;p&gt;As you correctly point out, starting vs-code from a terminal the west environment activated allows for selection of the stock toolchains in build. Once the builds complete, the `actions` pane shows the selected toolchain. (And more importantly, the proper toolchain is used -- turns out the three projects I am working on now -- 1 with nordic sdk, one with zephyr-stock 4.3.0 &amp;amp; one with zephyr-stock 3.7.1LTS all require their corresponding toolchains to properly complile code.)&lt;/p&gt;
&lt;p&gt;The reason I didn&amp;#39;t recognize your solution is that I was looking for something like &amp;quot;in settings set this json value&amp;quot; or some other method directly from the vs-code GUI. If you can confirm that the stock toolchains must be installed outside of the GUI and can not be selected except via the method you have identified, I&amp;#39;ll be glad to mark this as the accepted answer.&lt;/p&gt;
&lt;p&gt;Thanks again for your help &amp;amp; sorry I was so slow on the uptake.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Kent&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not install toolchain for 3rd party SDK (ie stock zephyr)</title><link>https://devzone.nordicsemi.com/thread/559620?ContentTypeID=1</link><pubDate>Tue, 27 Jan 2026 07:00:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e1db0ba0-4af6-4bb0-941d-7ae09deee570</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Did you try opening VS code from the terminal as I suggested in my previous reply?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not install toolchain for 3rd party SDK (ie stock zephyr)</title><link>https://devzone.nordicsemi.com/thread/559500?ContentTypeID=1</link><pubDate>Sat, 24 Jan 2026 22:37:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6378108e-65ba-43c0-a2fa-3c176954e3f5</guid><dc:creator>kent96822</dc:creator><description>&lt;p&gt;Do I need to add additional information to the ticket? Please let me know if I can help move this along. Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not install toolchain for 3rd party SDK (ie stock zephyr)</title><link>https://devzone.nordicsemi.com/thread/558771?ContentTypeID=1</link><pubDate>Thu, 15 Jan 2026 09:21:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c990756b-9ea8-4d2a-bba0-db30e4761188</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;First time I&amp;#39;m trying to use the Zephyr SDK instead of the NCS toolchain on macOS, but it seems to work fine as long as I open VS code from the terminal to let it inherit the build environment. Could you try the same on your end to see if it works for you as well?&lt;/p&gt;
&lt;p&gt;Opening VS code from terminal by running &amp;quot;code .&amp;quot; from the workspace directory&lt;/p&gt;
&lt;p&gt;(&lt;a href="https://code.visualstudio.com/docs/setup/mac#_launch-vs-code-from-the-command-line"&gt;https://code.visualstudio.com/docs/setup/mac#_launch-vs-code-from-the-command-line&lt;/a&gt;):&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/pastedimage1768469715429v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1768467392557v2.png" /&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1768468502833v3.png" /&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>