Pcl: [Windows] Installtion of PCL 1.10.1 for Windows using All in one installer

Created on 8 May 2020  路  34Comments  路  Source: PointCloudLibrary/pcl

Hi!. I wanted to work with PCL in my windows system and I also downloaded all in one installer and property sheet and added the bin folder locations of PCL and VTK to the Windows PATH environment variable.

But I am getting error like Cannot open source file "pcl/io/pcd_io.h"
and cannot open include file:"pcl/io/pcd_io.h:No such file or directory"

Please help me to fix this issue.

To be more precise i installed all in one installer which is latest version and added bin folder locations of PCL and VTK to the Windows PATH environment variable. After this i created one empty project in my visual studio 2017 and added existing property sheet file and then created one new main.cpp file and wrote one of the pcl header.And i got this issue.

question windows stale

All 34 comments

What is the " existing property sheet file " ?

The current exiting property sheet file is 1.8.0. There are only two property sheets one for 1.8.0 and other for 1.7.2 as per (https://github.com/PointCloudLibrary/pcl/releases) this source.

Thanks for the info @kunaltyagi . I downloaded property sheet for 1.10.1 and still i am getting same error

Which version have you installed?
Where is it installed?
Does the paths match in the property window of your project, for additional include folders?
ie.
image

I have used vcpkg, so don't mind my paths.

Some Windows users don't use/like CMake. I believe this property sheet request it's always from users who don't use CMake. It's a packaging issue and a matter of deciding if we want to support this at some point or not, but the trend exists.

A well written guide could probably help most cases :) I'm not sure if @UnaNancyOwen has made one?

PCL doesn't officially provide property sheets. PCL's position hasn't changed wrt this since 1.8.1. The link needs updating since the website had changed: new link

A well written guide could probably help most cases

I'm unaware of one on the wiki or website. Would be a welcome addition though (about 2 issues in a week referencing it)

github
@larshg . This is how it looks in my visual code. To be clear I am still a novice in c++ and using visual code(for c++ though). Till now i was using visual studio code for python but due to some timing problems i wanted to program in c++

The first one, ie:

C:\Program Files\PCL 1.10.1

should probably be:
C:\Program Files\PCL 1.10.1\include\pcl-1.10

Can you try post the expanded image of the additional directories?

@larshg.
git2

C:\Program Files\PCL 1.10.1
C:\Program Files\OpenNI2\Include
C:\Program Files\PCL 1.10.1\3rdParty\Boost\include\boost-1_72
C:\Program Files\PCL 1.10.1\3rdParty\Eigen\eigen
C:\Program Files\PCL 1.10.1\3rdParty\FLANN\include
C:\Program Files\PCL 1.10.1\3rdParty\Qhull\include
C:\Program Files\PCL 1.10.1\3rdParty\VTK\include\vtk-8.2

Update: Even I changed to :\Program Files\PCL 1.10.1\include\pcl-1.10, but still the error remains

And you can verify that pcl is actually installed in those paths?

@larshg . I think it is actually installed in that paths. I am not sure properly how to check it.
git3

But i think from above pic, i can assume that it installed in that paths only

Can you go into the include folder also and see if pcl-1.10.1 is there?

should probably be:
C:\Program Files\PCL 1.10.1\include\pcl-1.10

Meeh, I missed a .1 to the end.

C:\Program Files\PCL 1.10.1\include\pcl-1.10.1

git3

@larshg . It's there

I changed to C:\Program Files\PCL 1.10.1\include\pcl-1.10.1.

It should be the path that is shown in the explorer. You could even try and copy it from there and then add it to the property window.

@larshg. I did the same I copied path from explorer and added it in the property window.

PCL doesn't officially provide property sheets. PCL's position hasn't changed wrt this since 1.8.1. The link needs updating since the website had changed: new link

A well written guide could probably help most cases

I'm unaware of one on the wiki or website. Would be a welcome addition though (about 2 issues in a week referencing it)

It's one of those actionable items that if we decide to change at some point, will manifest itself in a larger adoption from the newbie windows community.

@SergioRAgostinho . That would be helpful!

I'll try later tonight to do an install with the all-in-one installer and see if I can figure out whats going on.

If the header files are present and you have the correct path set, it should be found. Can you right click on the include and "go to document" ?

@larshg . That would be extremely helpful for me.
git3. I was able to find header files if i am in this path. But if i am in C:\Program Files\PCL 1.10.1\include\pcl-1.10.1.i cant find any header files since there is more more folder inside that. I changed path also but still no use. :-(

Marking this as stale due to 30 days of inactivity. It will be closed in 7 days if no further activity occurs.

Just mention, we gave up on the All-In-One-Installer and went ahead with VCPKG.

So this might still need some love in regards of better tutorial, but there probably won't be anymore activity here.

It would be great if there is a tutorial for windows users. @larshg helped me with vcpkg and we went ahead. But there might be few persons who might face this problem in near future.

Just installed via All-In-One-Installer and wanted to point out that all of the pkgconfig .pc files installed have the wrong prefix path, it appears to be a relic of whoever builds the all-in-one-installer where their install prefix is set.
The installer suggested to install into C:/Program Files/PCL 1.11.0 but wherever you install it, the pkgconfig files will always point to C:/Program Files/PCL
image

I use PCL as an external dependency in another project I know how to get this working with the pkgconfig prefix issue, so I don't exactly need help. Just more a comment on what might give some people issues.

For the issue mentioned in the last comment. probably the easiest solution is just to create relocatable .pc files using the ${pcfiledir} variable, see https://github.com/ros2/ros2/issues/606#issuecomment-617603006 .

Marking this as stale due to 30 days of inactivity. It will be closed in 7 days if no further activity occurs.

It would be great if there is a tutorial for windows users. @larshg helped me with vcpkg and we went ahead. But there might be few persons who might face this problem in near future.

Hi,I have the same issue with you now,and I have tried everything I can think of,but it does not work. Do you find the solution to this problem? Any suggestions will be appriciated.

@ipandahuanhuan . Try with vcpkg. It should work

Thank you very much. I will try it later.

@ipandahuanhuan . Try with vcpkg. It should work

Hi, I think I've found the cause of the problem.
I copied the path in the include directory to notepad++, then I converted its code to ANSI code. It turned out that some of the paths had "? ".
After that I deleted the "?" , and copied the path back. Surprisingly, the original error has disappeared.
I hope that this is helpful to you.

Marking this as stale due to 30 days of inactivity. It will be closed in 7 days if no further activity occurs.

Closing due to inactivity

Was this page helpful?
0 / 5 - 0 ratings

Related issues

BjoB picture BjoB  路  4Comments

Micalson picture Micalson  路  4Comments

rmsalinas picture rmsalinas  路  3Comments

jacquelinekay picture jacquelinekay  路  5Comments

Passworteingeben picture Passworteingeben  路  3Comments