![]() MvIMPACT Acquire's internals are built using CMake ( ) and the public interface as well as the example applications are shipped with CMake support as well. Please refer to the Building And Linking Using CMake section for detailed instructions. This also automatically uses C++11 or above versions of the example code. The recommended way to build makefiles for compiling the SDK examples these days is by using CMake. MvIMPACT Acquire SDK has been compiled successfully with with clang 13.0.6, 14.0.0 and 15.0.6. ) and platforms can be generated very easily. for Eclipse) for a wide variety of other compilers(clang. ![]() But as mvIMPACT Acquire comes with CMake support files, makefiles and project files(e.g. The ready to use makefiles will only compile C++03 versions of the code. This also automatically uses C++11 or above versions of the example code if supported by the target compiler. However since CMake support has been added to the SDK these makefiles will no longer be maintained. Traditional makefiles as shipped with mvIMPACT Acquire at the time of writing will support a wide variety of target platforms. Note Since version 2.37.0 mvIMPACT Acquire is no longer shipped for Linux x86 and ARMsf! For details please also refer to Device And Operating System Support Across Released Versions.Īdditional information about supported compilers and minimum versions for libstdc++/libgcc can be found here MvIMPACT Acquire SDK has been compiled successfully with up to gcc 11.3. ![]() When generating makefiles or project files for a compiler that is not C++11 or above, be aware that using CMake will automatically result in legacy C++ code being used for the example applications. However as mvIMPACT Acquire comes with CMake support files makefiles and project files for a wide variety of other compilers can be generated. At the time of writing this was Visual Studio 2013. On Windows for the examples only one set of project files will be part of the installation packages.
0 Comments
Leave a Reply. |