IDS peak 2.20.0 / uEye+ firmware 3.80
IDS Peak comfortSDK, genericSDK, AFL, ICL, and IPL developer manuals are external documents.
Please contact us if you need these manuals.
When you create an application with IDS peak, there are several ways to create the project:
•Use a development environment (IDE) to open a CMake project directly, e.g. Qt Creator or Visual Studio 2017 or higher (recommended).
•Use predefined projects from the "samples" folder as a starting point.
•Use CMake to create your own projects.
|
It is recommended to use CMake for creating projects. CMake is preconfigured and makes the following settings automatically. |
comfortC
Include path |
$(IDS_PEAK_COMFORT_SDK_PATH)\api\include\ |
Includes |
#include <ids_peak_comfort_c/ids_peak_comfort_c.h> |
Linker |
$(IDS_PEAK_COMFORT_SDK_PATH)\api\lib\x86_64\ids_peak_comfort_c.lib |
Postbuild Events |
copy to output directory: $(IDS_PEAK_COMFORT_SDK_PATH)\api\lib\x86_64\*.dll |
genericC++
Include path |
$(IDS_PEAK_GENERIC_SDK_PATH)\api\include\ $(IDS_PEAK_GENERIC_SDK_PATH)\ipl\include\ $(IDS_PEAK_GENERIC_SDK_PATH)\afl\include\ |
Includes |
#include <peak/peak.hpp> #include <peak_ipl/peak_ipl.hpp> #include <peak_afl/peak_afl.hpp> |
Linker |
$(IDS_PEAK_GENERIC_SDK_PATH)\api\lib\x86_64\ids_peak.lib $(IDS_PEAK_GENERIC_SDK_PATH)\ipl\lib\x86_64\ids_peak_ipl.lib $(IDS_PEAK_GENERIC_SDK_PATH)\afl\lib\x86_64\ids_peak_afl.lib |
Postbuild Events |
copy to output directory: $(IDS_PEAK_GENERIC_SDK_PATH)\api\lib\x86_64\*.dll $(IDS_PEAK_GENERIC_SDK_PATH)\ipl\lib\x86_64\*.dll $(IDS_PEAK_GENERIC_SDK_PATH)\afl\lib\x86_64\*.dll |
genericC#
C# bindings: Use NuGet to get the C# bindings of IDS peak: https://www.nuget.org/profiles/IDS_Imaging
How to install the C# bindings for IDS peak is described in the ReadMe file.
|
Note: With the switch to NuGet, the namespaces were renamed to follow C# conventions. You find migration tables in the ReadMe file of the respective NuGet package, see https://www.nuget.org/profiles/IDS_Imaging. The following examples use the namespace as it was used up to IDS peak 2.19. |
Reference |
$(IDS_PEAK_GENERIC_SDK_PATH)\api\binding\dotnet\x86_64\ids_peak_dotnet.dll $(IDS_PEAK_GENERIC_SDK_PATH)\ipl\binding\dotnet\x86_64\ids_peak_ipl_dotnet.dll $(IDS_PEAK_GENERIC_SDK_PATH)\afl\binding\dotnet\x86_64\ids_peak_afl_dotnet.dll |
Postbuild Events |
copy to output directory: $(IDS_PEAK_GENERIC_SDK_PATH)\api\lib\x86_64\*.dll $(IDS_PEAK_GENERIC_SDK_PATH)\api\binding\dotnet\x86_64\*.dll $(IDS_PEAK_GENERIC_SDK_PATH)\ipl\lib\x86_64\*.dll $(IDS_PEAK_GENERIC_SDK_PATH)\ipl\binding\dotnet\x86_64\*.dll $(IDS_PEAK_GENERIC_SDK_PATH)\afl\lib\x86_64\*.dll $(IDS_PEAK_GENERIC_SDK_PATH)\afl\binding\dotnet\x86_64\*.dll |
genericPython
Python bindings: Use PyPi to get the Python bindings of IDS peak: https://pypi.org/user/IDS/
How to install the Python bindings for IDS peak is described in the ReadMe file.
Make sure that genericPython is properly installed. See the notes on Python in the ReadMe file.
Imports |
from ids_peak import ids_peak as peak from ids_peak_ipl import ids_peak_ipl as ipl from ids_peak_afl import ids_peak_afl as afl |
Notes: Under Linux, you include the paths to the dynamic libraries (*.so files) in the environment variable "LD_LIBRARY_PATH".
