At the time of this writing, the latest version of PCL is 1.9.1, and the address is here. But from all the indications on GitHub, 1.10 should be coming soon.
This article is done on the installation of PCL, and it is very detailed, so there is no need to repeat it.
The reason for this post is to explain that if you are using “AllInOne”, please do not select 1.9.1!!
Otherwise, when compiling release x64, it will report an error (x86 has not tried it, it will probably be enough). After a few hours of investigation, I saw someone mention this problem on GitHub, but the owner said that it is not recommended to use “AllInOne”, instead, use CMake, and then there is no such thing. After a long struggle, the guy decided to give up and use CMAKE to solve the problem.
After using Debug version n for a long time, I finally want to fix this problem today, so I want to try 1.9.0 instead of CMake, and then the problem will be solved…
Also, in some cases, PCL may need to be used with MFC, and its configuration is basically the same as if it were used on the console. However, there are a few issues that need to be noted, otherwise it will not compile.
1. Turn off SDL check: C/C++-> SDL check – & gt; No (/ SDL -)
2. Properties – & gt; Advanced – & gt; Use of MFC ->; Use MFC in a shared DLL, otherwise the following error will occur
3. VTKATOMIC. H with “::” before three “detail”
This article is done on the installation of PCL, and it is very detailed, so there is no need to repeat it.
The reason for this post is to explain that if you are using “AllInOne”, please do not select 1.9.1!!
Otherwise, when compiling release x64, it will report an error (x86 has not tried it, it will probably be enough). After a few hours of investigation, I saw someone mention this problem on GitHub, but the owner said that it is not recommended to use “AllInOne”, instead, use CMake, and then there is no such thing. After a long struggle, the guy decided to give up and use CMAKE to solve the problem.
After using Debug version n for a long time, I finally want to fix this problem today, so I want to try 1.9.0 instead of CMake, and then the problem will be solved…
Also, in some cases, PCL may need to be used with MFC, and its configuration is basically the same as if it were used on the console. However, there are a few issues that need to be noted, otherwise it will not compile.
1. Turn off SDL check: C/C++-> SDL check – & gt; No (/ SDL -)
2. Properties – & gt; Advanced – & gt; Use of MFC ->; Use MFC in a shared DLL, otherwise the following error will occur
3. VTKATOMIC. H with “::” before three “detail”
Read More:
- PCL environment configuration (pcl1.8.1, vs2017, win10)
- Vs2015 + PCL. 1.8.1 (win10) environment configuration
- Vtk8.2.0 (32bit + 64bit) compilation and installation test (win10 + vs2017 + Qt5)
- PCL environment construction (PCL 1.8.1 + vs 2017)
- Vs2013 error msb8031 solution today ran a MFC program, found that the error: error msb8031: building an MFC project for a non-U
- Installing Theano :Windows Installation Instructions
- Vs2017 compiles pcl1.8.1 with vtk8.0 and uses qt5.9.5
- Vs2012 compiling PCL dependency library vtk7.0
- Configuration problem of pcl1.9.1 under Windows 10 vs2017 (solved)
- Error code is 2502 / 2503 when installing MSI format installation package under win10 or win8
- Win10 install iTunes appears: “installation assembly microsoft.VC80 . CRT, tupe = Win32, version = 8.0.50727.6195 “…”
- [VTK] vtk8.2.0 + vs2015 + win10 compilation and configuration
- Win10 installation PostgreSQL error running… And installation process
- OpenGL class library and environment configuration under win10 and vs2015
- The experience of installing OpenGL in vs2017 under win7 system
- Configuring OpenGL development environment in win10 + vs2015 (including the method of installing 32-bit and 64 bit libraries)
- The problem of error in adaptation of Vue using vant mobile terminal rem
- Win10 must be optimized after installation to solve 100% disk occupation
- Installation and problems of texlive2017 in win10 system
- VTK + QT + vs compilation and installation configuration