<?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>Using the SDK with pc-ble-driver</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/20225/using-the-sdk-with-pc-ble-driver</link><description>Our product is a peripheral on the nRF51822. We develop on Mac and use gcc, make, etc with Visual Studio Code rather than Eclipse. Recently, we started getting close to production readiness and our contract manufacturer uses Windows. So I started writing</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 Mar 2017 16:33:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/20225/using-the-sdk-with-pc-ble-driver" /><item><title>RE: Using the SDK with pc-ble-driver</title><link>https://devzone.nordicsemi.com/thread/78808?ContentTypeID=1</link><pubDate>Tue, 14 Mar 2017 16:33:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5397aad7-7037-4f58-9abf-6e92010bb7b2</guid><dc:creator>Eliot Stock</dc:creator><description>&lt;p&gt;The short answer here is, yes, this is barking up the wrong tree. I tried porting the BLE db discovery module to Windows but given the dependency tree from there, I quickly ended up pulling in large parts of the SDK that were never going to be easily ported. The pc-ble-driver codebase alone is pretty low level and I&amp;#39;d encourage anyone who can to use the Python or Node.js bindings instead.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using the SDK with pc-ble-driver</title><link>https://devzone.nordicsemi.com/thread/78807?ContentTypeID=1</link><pubDate>Tue, 07 Mar 2017 13:35:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7914bdec-8e74-480d-9203-7779ae6eedb4</guid><dc:creator>Eliot Stock</dc:creator><description>&lt;p&gt;Both the Python binding and the Node.js binding to the pc-ble-driver code look great, but because this is a Windows machine on the factory floor, the CM is quite strict with the toolchain that we add to it and would like to avoid putting Iron Python or Node on there. Which is a shame. I&amp;#39;m trying to keep it strictly to C/C++/.NET code for now.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using the SDK with pc-ble-driver</title><link>https://devzone.nordicsemi.com/thread/78806?ContentTypeID=1</link><pubDate>Tue, 07 Mar 2017 06:42:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d3d73ed2-01d0-47a5-8ca6-2b539c3cbd4f</guid><dc:creator>J&amp;#248;rgen Kvalvaag</dc:creator><description>&lt;p&gt;If you don&amp;#39;t mind using python, you should check out the pc-ble-driver-py project, which is just a python wrapper for the pc-ble-driver. The current implementation comes with service discovery procedures, and is pip-installable. Linky: &lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver-py"&gt;github.com/.../pc-ble-driver-py&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>