meta-ros icon indicating copy to clipboard operation
meta-ros copied to clipboard

pcl: missing runtime dependency for dev-package

Open PeterProfessional opened this issue 7 years ago • 7 comments

I had a problem with the pcl recipe when I generated a cross compile toolchain: Compiling an application using the crosscompile toolchain failed because it used some pcl function that depended on eigen, which was not included in the toolchain's rootfs. I fixed the issue by adding: RDEPENDS_${PN}-dev += " libeigen" to the pcl recipe. I thought you might want to include this or an equivalent fix in the repository since others might have the same problem.

PeterProfessional avatar Jul 31 '17 09:07 PeterProfessional

Did you already use the commits on pull request #519 to build the cross-compile tool chain?

bulwahn avatar Jul 31 '17 09:07 bulwahn

No, I actually had the issue back in April. Perhaps I'm missing something but I don't see the relation between this issue and #519 To clarify, I did neither use any ros-recipes nor any sdk-recipe from the meta-ros layer but only the pcl-recipe.

PeterProfessional avatar Jul 31 '17 10:07 PeterProfessional

Well, I just wanted to understand if you build a tool chain for a ROS package, or if you just use the pcl recipe in the meta-ros layer. As you said, it is the latter. Please open a pull request with your commit, then we will review, test and merge it.

bulwahn avatar Jul 31 '17 11:07 bulwahn

I looked into it and wondered if there would be an alternative solution. If I am not mistaken, the libeigen recipe is the peculiarity that in all its dependencies needs to be included as rdepends-dev dependency. So if bitbake allows that, it would be best if we could include some annotation in the libeigen recipe rather than all the recipes that depend on libeigen.

bulwahn avatar Aug 25 '17 07:08 bulwahn

@PeterProfessional < Can this issue be closed?

herb-kuta-lge avatar Feb 07 '20 16:02 herb-kuta-lge

The issue was not addressed yet (as far as I know), so I would not close it. I see that it is quite old and the chances that someone will invest the time for it grow somewhat thinner but maybe I'll find the time for a fix in the next 2 months.

PeterProfessional avatar Feb 10 '20 09:02 PeterProfessional

@PeterProfessional any update on this? We don't plan to do any new changes to old legacy branch, if you don't plan to fix it yourself, then please close it.

shr-project avatar Jul 28 '20 12:07 shr-project

This appears to be against the old legacy branch. Closing it as it is over 5 years old and we don't intend to support the legacy branch.

robwoolley avatar Nov 17 '23 02:11 robwoolley