Re: [oe] [yocto] Bug in Open CV receipt
On Thu, Jul 23, 2015 at 11:30 AM, Otavio Salvador otavio.salva...@ossystems.com.br wrote: On Thu, Jul 23, 2015 at 12:05 PM, Victor Rodriguez vm.ro...@gmail.com wrote: On Wed, Jul 22, 2015 at 7:35 AM, Otavio Salvador otavio.salva...@ossystems.com.br wrote: On Tue, Jul 21, 2015 at 11:57 AM, Victor Rodriguez vm.ro...@gmail.com wrote: Few weeks ago I was having some problems with open CV receipt. In the begining I toght I was adding opencv tro my core-image-minimal-xfce just with this: IMAGE_INSTALL_append = gcc gcc-dev openssh php mariadb opencv Now after booting the image I realize that none of the libraries for open stack were added to my image What I had to do was the following: IMAGE_INSTALL_append = libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev libopencv-objdetect-dev libopencv-ml-dev opencv-staticdev python-opencv Even last night when one of the opencv developers ask me for python opencv I had to add the last part python-opencv. That is not cool at all . If I add opencv in the beginning I assume we are more than cool with that and yocto will add all the packages . Unless I am doing something wrong, in taht case I am more than happy to get the feedback. Thanks a lot for all the help . If someone else can reproduce this bug I am more than happy to report it in bugzila (not sure the URL) You should add the dev-pkgs and tools-sdk image features for the image, not mangle it manually. I think the best solution is create a package group that will keep backward compatibility and aloud packages exist as expected Sorry but this does not make sense. The image recipe you described is not using the framework structure for this and this is the problem you should address not bloat the oe-core itself. Check core-image class for it. Thanks a lot for the help and answer these mails I will create a RFC patch just for this recipe and see what happen The problem is that when I add opencv to the image nothing is added not even the capabilities to run a binary with this library nor the capability to do development I will send the patch to the open embedded and see what the community think Best regards Victor Rodriguez -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [yocto] Bug in Open CV receipt
On Wed, Jul 22, 2015 at 7:35 AM, Otavio Salvador otavio.salva...@ossystems.com.br wrote: On Tue, Jul 21, 2015 at 11:57 AM, Victor Rodriguez vm.ro...@gmail.com wrote: Few weeks ago I was having some problems with open CV receipt. In the begining I toght I was adding opencv tro my core-image-minimal-xfce just with this: IMAGE_INSTALL_append = gcc gcc-dev openssh php mariadb opencv Now after booting the image I realize that none of the libraries for open stack were added to my image What I had to do was the following: IMAGE_INSTALL_append = libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev libopencv-objdetect-dev libopencv-ml-dev opencv-staticdev python-opencv Even last night when one of the opencv developers ask me for python opencv I had to add the last part python-opencv. That is not cool at all . If I add opencv in the beginning I assume we are more than cool with that and yocto will add all the packages . Unless I am doing something wrong, in taht case I am more than happy to get the feedback. Thanks a lot for all the help . If someone else can reproduce this bug I am more than happy to report it in bugzila (not sure the URL) You should add the dev-pkgs and tools-sdk image features for the image, not mangle it manually. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ yocto mailing list yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto I think the best solution is create a package group that will keep backward compatibility and aloud packages exist as expected -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [yocto] Bug in Open CV receipt
On Thu, Jul 23, 2015 at 12:05 PM, Victor Rodriguez vm.ro...@gmail.com wrote: On Wed, Jul 22, 2015 at 7:35 AM, Otavio Salvador otavio.salva...@ossystems.com.br wrote: On Tue, Jul 21, 2015 at 11:57 AM, Victor Rodriguez vm.ro...@gmail.com wrote: Few weeks ago I was having some problems with open CV receipt. In the begining I toght I was adding opencv tro my core-image-minimal-xfce just with this: IMAGE_INSTALL_append = gcc gcc-dev openssh php mariadb opencv Now after booting the image I realize that none of the libraries for open stack were added to my image What I had to do was the following: IMAGE_INSTALL_append = libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev libopencv-objdetect-dev libopencv-ml-dev opencv-staticdev python-opencv Even last night when one of the opencv developers ask me for python opencv I had to add the last part python-opencv. That is not cool at all . If I add opencv in the beginning I assume we are more than cool with that and yocto will add all the packages . Unless I am doing something wrong, in taht case I am more than happy to get the feedback. Thanks a lot for all the help . If someone else can reproduce this bug I am more than happy to report it in bugzila (not sure the URL) You should add the dev-pkgs and tools-sdk image features for the image, not mangle it manually. I think the best solution is create a package group that will keep backward compatibility and aloud packages exist as expected Sorry but this does not make sense. The image recipe you described is not using the framework structure for this and this is the problem you should address not bloat the oe-core itself. Check core-image class for it. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [yocto] Bug in Open CV receipt
On Tue, Jul 21, 2015 at 3:49 PM, Leonardo Sandoval leonardo.sandoval.gonza...@linux.intel.com wrote: On 07/21/2015 09:57 AM, Victor Rodriguez wrote: Hi team Few weeks ago I was having some problems with open CV receipt. In the begining I toght I was adding opencv tro my core-image-minimal-xfce just with this: IMAGE_INSTALL_append = gcc gcc-dev openssh php mariadb opencv Now after booting the image I realize that none of the libraries for open stack were added to my image What I had to do was the following: IMAGE_INSTALL_append = libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev libopencv-objdetect-dev libopencv-ml-dev opencv-staticdev python-opencv A recipe can produce several packages. As I can see on opencv recipe, it can produced the following ones: PACKAGES=opencv-staticdev opencv-dev opencv-dbg opencv-doc opencv opencv-apps python-opencv and dynamic ones (depending on what else you have install) PACKAGES_DYNAMIC=^opencv-locale-.* ^libopencv-.* For the opencv case, it happens that the package opencv is empty, so you need to append the other sub-packages it produces into your IMAGE_INSTALL variable. So, it is not a bug, this is expected. In my humble opinion this should change for OpenCV. But I would love to hear the feedback from others Even last night when one of the opencv developers ask me for python opencv I had to add the last part python-opencv. That is not cool at all . If I add opencv in the beginning I assume we are more than cool with that and yocto will add all the packages . Unless I am doing something wrong, in taht case I am more than happy to get the feedback. Thanks a lot for all the help . If someone else can reproduce this bug I am more than happy to report it in bugzila (not sure the URL) Hope it helps to cut the time of some others Best regards Victor Rodriguez -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
