<?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>nRF Connect for VS Code misleading warning when using CONFIG_PICOLIBC</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/106049/nrf-connect-for-vs-code-misleading-warning-when-using-config_picolibc</link><description>I am working with v2.5.0 toolchain and SDK, and the ASSET_TRACKER_V2 application. I configured the build for nRF9160dk_nrf9160 and selected all defaults. Note that the prj.conf for the project has CONFIG_PICOLIBC=y which sounds nice to my ears (c library</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 27 Nov 2023 16:06:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/106049/nrf-connect-for-vs-code-misleading-warning-when-using-config_picolibc" /><item><title>RE: nRF Connect for VS Code misleading warning when using CONFIG_PICOLIBC</title><link>https://devzone.nordicsemi.com/thread/457649?ContentTypeID=1</link><pubDate>Mon, 27 Nov 2023 16:06:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dd3920d8-e9c5-4a5c-94b9-ff8c99a02f85</guid><dc:creator>Burt</dc:creator><description>&lt;p&gt;That&amp;#39;s excellent news. Thank you, Hung.&lt;/p&gt;
&lt;p&gt;Burt&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect for VS Code misleading warning when using CONFIG_PICOLIBC</title><link>https://devzone.nordicsemi.com/thread/457636?ContentTypeID=1</link><pubDate>Mon, 27 Nov 2023 15:45:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:521effca-e3bd-40f7-bfba-646e7167c29b</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi again Burt,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I have reported the issue to our team. They have confirmed it&amp;#39;s a bug and a fix will be released, hopefully by the end of this week.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect for VS Code misleading warning when using CONFIG_PICOLIBC</title><link>https://devzone.nordicsemi.com/thread/457603?ContentTypeID=1</link><pubDate>Mon, 27 Nov 2023 14:36:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2e6b1f7d-8352-4bf1-861a-8f24c6c71a2c</guid><dc:creator>Burt</dc:creator><description>&lt;p&gt;Hello Hung,&lt;/p&gt;
&lt;p&gt;I am only referring to the IntelliSense warning, and not warnings from compiling. I want to know the NS plan and schedule for fixing this issue. Please confer with the developers of the nRF Connect for VS Code extension and provide me with details regarding the plans to fix the issues that I have seen, and other issues that you have seen (ones you mention in your third sentence). Thank you if you can provide me with the extra details. I wish to be able to promote the extension to my team positively, without reservations.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect for VS Code misleading warning when using CONFIG_PICOLIBC</title><link>https://devzone.nordicsemi.com/thread/457557?ContentTypeID=1</link><pubDate>Mon, 27 Nov 2023 12:45:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de42894f-786c-4685-b9e5-df666c8183c9</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Burt,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Do you have any issue when compiling the code ? Do you receive any error or warning by the compiler ?&amp;nbsp;&lt;br /&gt;We have seen issues where VSCode extension&amp;nbsp;couldn&amp;#39;t detect all the dependencies and gave wrong warning or interpretation.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>