This GitHub repository contains code samples that demonstrate how to use Microsoft's Azure Kinect DK Sensor and Body Tracking SDKs.
For more information about the Azure Kinect DK and available documentation, see [Azure.com/Kinect] (https://azure.microsoft.com/services/kinect-dk/)
Each sample includes a README file that explains how to run and use the sample.
[]
(https://microsoft.visualstudio.com/Analog/_build/latest?definitionId=41402&branchName=master)
We welcome your contributions and suggestions! Please open new issues in our [Azure Kinect Sensor SDK repository] (https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues). Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com. When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
Complete your developer profile here to get connected with our Mixed Reality Developer Program. You will receive the latest on our developer tools, events, and early access offers.
Due to the samples being provided from various sources they may only build for Windows or Linux. To keep the barrier for adding new samples low we only require that the sample works in one place.
If the project has Visual Studio solution open it and build. CMake is not currently supported for Windows, though we support the community expanding on this.
For building with Linux, CMake is used. Build from a git clone, we do not support building from a ZIP file.
Install the prerequisites
apt install libk4abt1.1-dev
apt install libxi-dev
From the root of the git project
mkdir build
cd build
cmake .. -GNinja
ninja
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.