This is the Ubitrack device_tracker_vicon submodule.
The device_tracker_vicon contains components to connect to Vicon Tracking Services via network.
$ conan remote add camposs "https://conan.campar.in.tum.de/api/conan/conan-camposs"
$ conan remote add ubitrack "https://conan.campar.in.tum.de/api/conan/conan-ubitrack"
If you handle multiple dependencies in your project is better to add a conanfile.txt
[requires]
ubitrack_device_tracker_vicon/1.3.0@ubitrack/stable
[generators]
cmake
txt
Complete the installation of requirements for your project running:
$ mkdir build && cd build && conan install ..
Note: It is recommended that you run conan install from a build directory and not the root of the project directory. This is because conan generates conanbuildinfo files specific to a single build configuration which by default comes from an autodetected default profile located in ~/.conan/profiles/default . If you pass different build configuration options to conan install, it will generate different conanbuildinfo files. Thus, they shoudl not be added to the root of the project, nor committed to git.
The example below shows the commands used to publish to campar conan repository. To publish to your own conan respository (for example, after forking this git repository), you will need to change the commands below accordingly.
The following command both runs all the steps of the conan file, and publishes the package to the local system cache. This includes downloading dependencies from "build_requires" and "requires" , and then running the build() method.
$ conan create . ubitrack/stable
$ conan upload -r ubitrack ubitrack_device_tracker_vicon/1.3.0@ubitrack/stable