From 3cda7aede81b55796a1111163e9d0f8a57ca5e4e Mon Sep 17 00:00:00 2001 From: Matthias Ringwald Date: Thu, 3 May 2018 11:25:04 +0200 Subject: [PATCH] windows: add info on required toolchain --- port/windows-h4/README.md | 24 +++++++++++++++++++++++- port/windows-winusb/README.md | 26 +++++++++++++++++++++++++- 2 files changed, 48 insertions(+), 2 deletions(-) diff --git a/port/windows-h4/README.md b/port/windows-h4/README.md index 69cc62105..d741fb894 100644 --- a/port/windows-h4/README.md +++ b/port/windows-h4/README.md @@ -4,7 +4,29 @@ The Windows-H4 port uses the native run loop and allows to use Bluetooth Control Make sure to manually reset the Bluetooth Controller before starting any of the examples. +## Toolchain + +The port requires a Unix-like toolchain. We successfully used [mingw-w64](https://mingw-w64.org/doku.php) to compile and run the examples. mingw64-w64 is based on [MingW](mingw.org) which has a good summary 'MinGW provides a complete Open Source programming tool set which is suitable for the development of native MS-Windows applications, and which do not depend on any 3rd-party C-Runtime DLLs.' + +We've used the Msys2 package available from their [downloads page](https://mingw-w64.org/doku.php/download) on Windows 10, 64-bit and use the MSYS2 MinGW 32-bit start menu item to compile 32-bit binaries that run on both 32/64-bit systems. + +IN the MSYS2 shell, you can install git, winpty, and python with pacman: + + $ pacman -S git + $ pacman -S winpty + $ pacman -S python + +## Compilation + +With mingw64 installed, just go to the port/windows-winusb directory and run make + + $ cd btstack/port/windows-winusb + $ make + +## Console Output + When running the examples in the MSYS2 shell, the console input (via btstack_stdin_support) doesn't work. It works in the older MSYS and also the regular CMD.exe environment. Another option is to install WinPTY and then start the example via WinPTY like this: - $ winpty ./hfp_hf_demo.exe + $ winpty ./spp_and_le_counter.exe + diff --git a/port/windows-winusb/README.md b/port/windows-winusb/README.md index 29451425e..d6316f76c 100644 --- a/port/windows-winusb/README.md +++ b/port/windows-winusb/README.md @@ -2,9 +2,12 @@ The Windows-WinUSB port uses the native run loop and WinUSB API to access a USB Bluetooth dongle. +## Access to Bluetooth USB Dongle with Zadig + To allow libusb or WinUSB to access an USB Bluetooth dongle, you need to install a special device driver to make it accessible to user space processes. It works like this: + - Download [Zadig](http://zadig.akeo.ie) - Start Zadig - Select Options -> “List all devices” @@ -12,7 +15,28 @@ It works like this: - Select WinUSB (libusb) in the right pull pull down list - Select “Replace Driver” +## Toolchain + +The port requires a Unix-like toolchain. We successfully used [mingw-w64](https://mingw-w64.org/doku.php) to compile and run the examples. mingw64-w64 is based on [MingW](mingw.org) which has a good summary 'MinGW provides a complete Open Source programming tool set which is suitable for the development of native MS-Windows applications, and which do not depend on any 3rd-party C-Runtime DLLs.' + +We've used the Msys2 package available from their [downloads page](https://mingw-w64.org/doku.php/download) on Windows 10, 64-bit and use the MSYS2 MinGW 32-bit start menu item to compile 32-bit binaries that run on both 32/64-bit systems. + +IN the MSYS2 shell, you can install git, winpty, and python with pacman: + + $ pacman -S git + $ pacman -S winpty + $ pacman -S python + +## Compilation + +With mingw64 installed, just go to the port/windows-winusb directory and run make + + $ cd btstack/port/windows-winusb + $ make + +## Console Output + When running the examples in the MSYS2 shell, the console input (via btstack_stdin_support) doesn't work. It works in the older MSYS and also the regular CMD.exe environment. Another option is to install WinPTY and then start the example via WinPTY like this: - $ winpty ./hfp_hf_demo.exe + $ winpty ./spp_and_le_counter.exe