Azure IoT Gateway SDK
New Features
Add support for modules running in .NET Core (see Known Issues)
Allow Java modules to implement a default ctor that doesn't call Create
Use versioned CMake packages for dependencies
Changes/Bug Fixes
When building dependencies, don't build azure-iot-sdk-c samples
Fix out-of-order delivery of messages to Node.js modules
Fix .NET release build configurations
Fix unit test failures in Release builds
Fix #109 by removing the sample bitbake file in favor of Azure recipes from Intel
Fix #118 by exposing an option to use cross-platform UUID
Update submodule references to fix #119
Validate "debug.port" JSON value in Java module config
Get rid of VECTOR errors in stdout
Fix #120 by removing the --clean
option from the bash build script
Specify CMake generator explicitly in 32-bit Windows builds
Fix #104 by:
- Propagating build config (Release, Debug) when building dependencies
- Generating symbols on Windows for release build configurations
- Supporting rebuilding of dependencies in build scripts
Fix bug #96 by making the call to a Node.js module's Create function synchronous
Update documentation & config JSON for Node.js module sample
Remove uses of crtdbg in favor of VLD
Pass toolchain to CMake in Wind River Linux build script
Remove C++11 uniform initializers to workaround GCC 4.8 bug
Replace develop
with master
in Git-aware documentation and scripts
Merge pull request #98 from @SummerSun
Describe the current gateway architecture in a Visio diagram
Known Issues
An exception is thrown when a module written for .NET Core is loaded by a gateway application on 32-bit Windows. This bug is under investigation. 64-bit Windows, as well as 32- and 64-bit Ubuntu, are not affected.