C++ (Windows)

You are viewing an old version of the documentation. You can switch to the documentation of the latest version by clicking the top-right corner of the page.

This topic introduces how to configure the Mech-Eye API C++ samples with CMake and then build the samples with Visual Studio on Windows.

Sample List

The following samples are currently provided:

  • AcquireProfileData: Acquire the profile data, generate the intensity image and depth map, and save the images.

  • AcquireProfileDataUsingCallback: Acquire the profile data using a callback function, generate the intensity image and depth map, and save the images.

  • AcquirePointCloud: Acquire the profile data, generate the point cloud, and save the point cloud in the CSV and PLY formats.

  • ManageUserSets: Manage parameter groups, such as obtaining the names of all parameter groups, adding a parameter group, switching the parameter group, and saving parameter settings to the parameter group.

  • RegisterProfilerEvent: Define and register the callback function for monitoring the laser profiler connection status.

  • UseVirtualDevice: Acquire the profile data stored in a virtual device, generate the intensity image and depth map, and save the images.

Prerequisites

In order to use the C++ samples of Mech-Eye API, the following prerequisites must be satisfied:

Obtain Samples

C++ samples are included in the installation path of Mech-Eye SDK or can be obtained from GitHub by cloning. The samples in the installation path are the version at the time of Mech-Eye SDK release. The version on GitHub may contain the latest changes.

  • The samples in the installation path are located in xxx/Mech-Eye SDK-2.3.0/API/samples/cpp/profiler.

  • The samples cloned from GitHub are located in xxx/mecheye_cpp_samples/profiler.

Install Required Software

In order to use the C++ samples of Mech-Eye API, Mech-Eye SDK, CMake and Visual Studio must be installed.

Install the Latest Version of Mech-Eye SDK

Please install or upgrade Mech-Eye SDK according to Mech-Eye SDK Installation Guide.

Install CMake (Version 3.2 or Above)

  1. Download CMake: download the installer to the right of Windows x64 Installer.

    cmake download

  2. When installing, select the following two options to add CMake to environment variables and create a desktop shortcut for CMake.

    • Add CMake to the system PATH for all users

    • Create Cmake Desktop Icon

cmake 1

Install Visual Studio (Version 2017 or Above)

  1. Download the Visual Studio installer.

  2. When installing, select the following two workloads in the Desktop & Mobile category, and then click Install.

    • Desktop development with C++

    • Universal Windows Platform development

Please restart your computer after installing Visual Studio. If you still need to install the optional software, you can restart your computer after all installations have been completed.

(Optional) Install Dependent Software Libraries

Some samples contain functions that depend on the following third-party software libraries. If you need to use the samples listed in the table below, you must install the software libraries on which the samples depend.

  • OpenCV: version 3.4.5 or above

If any of the optional software libraries is not installed, then you must complete the steps in Disable Unneeded Samples (Optional) before configuring the samples.

Refer to the following table for the samples that depend on third-party software libraries.

Sample

AcquireProfileData

AcquireProfileDataUsingCallback

UseVirtualDevice

Install OpenCV

  1. Download and install OpenCV. Note down the installation path of OpenCV.

  2. Add OpenCV to environment variables:

    1. Right-click This PC on the desktop and select Properties.

    2. Click Advanced system settings, and in the pop-up System Properties window, click Environment Variables to open the Environment Variables window.

    3. Double-click Path in the user variables to enter the Edit environment variable page. Click New in the upper-right and add the following paths one by one. Then, click OK to exit the window.

      • xxx/OpenCV/build/x64/vc14/bin

      • xxx/OpenCV/build/x64/vc14/lib

It is recommended to restart your computer after adding the environmental variables. If not restarted, the environmental variables added may not be effective.

Build and Run Samples

You can build all samples at once or build a single sample individually.

The paths provided in this section correspond to the samples included in the installation path. If you are using the samples cloned from GitHub, please modify the paths correspondingly.

Disable Unneeded Samples (Optional)

If you did not install some of the optional software libraries and still want to build all samples at once, then you must complete the steps in this section. Otherwise, an error will occur during the configuration of samples using CMake.

If you do not need the samples that depend on OpenCV, please edit the CMakeLists file to disable these samples before building all samples at a time.

  1. Open CMakeLists.txt in xxx/Mech-Eye SDK-2.3.0/API/samples/cpp/profiler.

  2. Edit the line containing options: find the line of option(USE_OPENCV…​), change ON at the end of the line to OFF to disable the samples that depend on OpenCV.

  3. Save the changes and close CMakeLists.txt.

Configure Samples in CMake

  1. Right-click CMake and select Run as administrator.

  2. Enter the paths of source code and binaries.

    • To build all samples at once, enter the following paths.

      Where is the source code

      xxx/Mech-Eye SDK-2.3.0/API/samples/cpp/profiler

      Where to build the binaries

      xxx/Mech-Eye SDK-2.3.0/API/samples/cpp/profiler/build

    • To build one sample individually, enter the following paths. Replace SampleName with the name of the sample.

      Where is the source code

      xxx/Mech-Eye SDK-2.3.0/API/samples/cpp/profiler/SampleName

      Where to build the binaries

      xxx/Mech-Eye SDK-2.3.0/API/samples/cpp/profiler/SampleName/build

  3. Click Configure in the bottom to open the configuration page. Select Visual Studio version, and set the platform to x64. Then, click Finish. When the configuration completes, the log will display Configuring done.

    configuration 1

  4. Click Generate to generate Visual Studio solution. When the generation completes, the log will display Generating done. Then, click Open Project to open the solution in Visual Studio.

Build Samples in Visual Studio

  1. In Visual Studio toolbar, change the solution configuration from Debug to Release.

  2. In the menu bar, select Build  Build Solution. An executable file (.exe) is generated for each sample. The executable files are saved to the Release folder, located in the Where to build the binaries directory that you entered in CMake.

Run Samples

You can run the samples in Visual Studio after building them, or run the samples by double-clicking the executable files.

Run a Sample in Visual Studio

  1. In the Solution Explorer panel, right-click a sample, and select Set as Startup Project.

  2. Click Local Windows Debugger in the toolbar to run the sample.

    While the sample is running, input the index of the laser profiler to which you want to connect according to the instruction, and press Enter to connect to the laser profiler.

  3. If image and/or point cloud files are saved by the sample, you can find the files in the build folder (the Where to build the binaries directory that you entered in CMake).

Run the Executable File of a Sample

  1. Navigate to the Where to build the binaries directory that you entered in CMake, and open the Release folder.

  2. Run the executable file with the same name as the sample.

    While the sample is running, input the index of the laser profiler to which you want to connect according to the instruction, and press Enter to connect to the laser profiler.

  3. If image and/or point cloud files are saved by the sample, you can find the files in the Release folder.

We Value Your Privacy

We use cookies to provide you with the best possible experience on our website. By continuing to use the site, you acknowledge that you agree to the use of cookies. If you decline, a single cookie will be used to ensure you're not tracked or remembered when you visit this website.

  • Preference
  • I accept
  • I don't accept