Yocto Poky 2.4.1 - Remove python3 from build

Yocto Poky 2.4.1 - Remove python3 from build

[Marwen BRIKCHA]

[-- Attachment #1: Type: text/plain, Size: 291 bytes --]

Hello,

I'm using Yocto Poky 2.4.1 and bitbake version 1.6.0 to build a xilinx
embedded linux for zcu102 board.

I've integrated OpenCV libraries on my image.

So, I want to remove python3 from image build .

Can you help me here on how to do that ?

----
Best regards,
Marwen

[-- Attachment #2: Type: text/html, Size: 469 bytes --]

Re: Yocto Poky 2.4.1 - Remove python3 from build

[Burton, Ross]

Disable the 'python3' PACKAGECONFIG in the opencv recipe.

https://www.yoctoproject.org/docs/2.5.1/ref-manual/ref-manual.html#var-PACKAGECONFIG

Ross
On Tue, 16 Oct 2018 at 11:17, Marwen BRIKCHA <marwen.brikcha@gmail.com> wrote:
>
> Hello,
>
> I'm using Yocto Poky 2.4.1 and bitbake version 1.6.0 to build a xilinx embedded linux for zcu102 board.
>
> I've integrated OpenCV libraries on my image.
>
> So, I want to remove python3 from image build .
>
> Can you help me here on how to do that ?
>
> ----
> Best regards,
> Marwen
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: Yocto Poky 2.4.1 - Remove python3 from build

[Marwen BRIKCHA]

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

Hello Ross,

I've set in my receipe opencv_3.%.bappend
PACKAGECONFIG = "eigen jpeg png tiff v4l libv4l gstreamer"
EXTRA_OECMAKE_append = " \
                  -DBUILD_PYTHON_SUPPORT=OFF \
                  -DBUILD_opencv_python3=OFF \
                 "
But alway opencv build python 3 dependencies in my images.
It's weird.

*$> bitbake -e opencv | grep "PACKAGECONFIG", I got :*
PACKAGECONFIG=" eigen jpeg png tiff v4l libv4l gstreamer"
and some other log that show -DBUILD_PYTHON_SUPPORT=OFF
-DBUILD_opencv_python3=OFF

Any help ?

Br,
Marwen



Le mar. 16 oct. 2018, à 13 h 21, Burton, Ross <ross.burton@intel.com> a
écrit :

> Disable the 'python3' PACKAGECONFIG in the opencv recipe.
>
>
> https://www.yoctoproject.org/docs/2.5.1/ref-manual/ref-manual.html#var-PACKAGECONFIG
>
> Ross
> On Tue, 16 Oct 2018 at 11:17, Marwen BRIKCHA <marwen.brikcha@gmail.com>
> wrote:
> >
> > Hello,
> >
> > I'm using Yocto Poky 2.4.1 and bitbake version 1.6.0 to build a xilinx
> embedded linux for zcu102 board.
> >
> > I've integrated OpenCV libraries on my image.
> >
> > So, I want to remove python3 from image build .
> >
> > Can you help me here on how to do that ?
> >
> > ----
> > Best regards,
> > Marwen
> > --
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 2562 bytes --]

Re: Yocto Poky 2.4.1 - Remove python3 from build

[Burton, Ross]

How do you know that opencv is responsible for pulling Python 3 into
your images?

Ross
On Tue, 16 Oct 2018 at 13:59, Marwen BRIKCHA <marwen.brikcha@gmail.com> wrote:
>
> Hello Ross,
>
> I've set in my receipe opencv_3.%.bappend
> PACKAGECONFIG = "eigen jpeg png tiff v4l libv4l gstreamer"
> EXTRA_OECMAKE_append = " \
>                   -DBUILD_PYTHON_SUPPORT=OFF \
>                   -DBUILD_opencv_python3=OFF \
>                  "
> But alway opencv build python 3 dependencies in my images.
> It's weird.
>
> $> bitbake -e opencv | grep "PACKAGECONFIG", I got :
> PACKAGECONFIG=" eigen jpeg png tiff v4l libv4l gstreamer"
> and some other log that show -DBUILD_PYTHON_SUPPORT=OFF      -DBUILD_opencv_python3=OFF
>
> Any help ?
>
> Br,
> Marwen
>
>
>
> Le mar. 16 oct. 2018, à 13 h 21, Burton, Ross <ross.burton@intel.com> a écrit :
>>
>> Disable the 'python3' PACKAGECONFIG in the opencv recipe.
>>
>> https://www.yoctoproject.org/docs/2.5.1/ref-manual/ref-manual.html#var-PACKAGECONFIG
>>
>> Ross
>> On Tue, 16 Oct 2018 at 11:17, Marwen BRIKCHA <marwen.brikcha@gmail.com> wrote:
>> >
>> > Hello,
>> >
>> > I'm using Yocto Poky 2.4.1 and bitbake version 1.6.0 to build a xilinx embedded linux for zcu102 board.
>> >
>> > I've integrated OpenCV libraries on my image.
>> >
>> > So, I want to remove python3 from image build .
>> >
>> > Can you help me here on how to do that ?
>> >
>> > ----
>> > Best regards,
>> > Marwen
>> > --
>> > _______________________________________________
>> > yocto mailing list
>> > yocto@yoctoproject.org
>> > https://lists.yoctoproject.org/listinfo/yocto

Re: Yocto Poky 2.4.1 - Remove python3 from build

[Burton, Ross]

On Tue, 16 Oct 2018 at 14:06, Marwen BRIKCHA <marwen.brikcha@gmail.com> wrote:
>
> because, when i run :
> :
> $> bitbake -v opencv
> I can see that python3 is fetched, configure, ... etc
> So, i think it the responsible for this.

Please remember to CC the list.

Python being built doesn't lead to Python being installed in the
image.  Have a look at the image manifest (in deploy/images) or look
at what is actually installed inside the image.

Ross

Re: Yocto Poky 2.4.1 - Remove python3 from build

[Marwen BRIKCHA]

[-- Attachment #1: Type: text/plain, Size: 711 bytes --]

Yes. I've seen compilation log and it does do_install in final image.
It's installed in /usr/lib64/python3.5 on RootFS.

Le mer. 17 oct. 2018, à 00 h 48, Burton, Ross <ross.burton@intel.com> a
écrit :

> On Tue, 16 Oct 2018 at 14:06, Marwen BRIKCHA <marwen.brikcha@gmail.com>
> wrote:
> >
> > because, when i run :
> > :
> > $> bitbake -v opencv
> > I can see that python3 is fetched, configure, ... etc
> > So, i think it the responsible for this.
>
> Please remember to CC the list.
>
> Python being built doesn't lead to Python being installed in the
> image.  Have a look at the image manifest (in deploy/images) or look
> at what is actually installed inside the image.
>
> Ross
>

[-- Attachment #2: Type: text/html, Size: 1104 bytes --]

Re: Yocto Poky 2.4.1 - Remove python3 from build

[Burton, Ross]

Easiest way to determine what is pulling it in is to try removing the
package on the target using the package manager.  That will tell you
what dependencies are keeping it in.

Ross
On Wed, 17 Oct 2018 at 08:32, Marwen BRIKCHA <marwen.brikcha@gmail.com> wrote:
>
> Yes. I've seen compilation log and it does do_install in final image.
> It's installed in /usr/lib64/python3.5 on RootFS.
>
> Le mer. 17 oct. 2018, à 00 h 48, Burton, Ross <ross.burton@intel.com> a écrit :
>>
>> On Tue, 16 Oct 2018 at 14:06, Marwen BRIKCHA <marwen.brikcha@gmail.com> wrote:
>> >
>> > because, when i run :
>> > :
>> > $> bitbake -v opencv
>> > I can see that python3 is fetched, configure, ... etc
>> > So, i think it the responsible for this.
>>
>> Please remember to CC the list.
>>
>> Python being built doesn't lead to Python being installed in the
>> image.  Have a look at the image manifest (in deploy/images) or look
>> at what is actually installed inside the image.
>>
>> Ross

Re: Yocto Poky 2.4.1 - Remove python3 from build

[Burton, Ross]

Alternatively if you're using RPMs, you can set PACKAGE_EXCLUDE =
"python3-core":

Error:
 Problem 1: conflicting requests
  - nothing provides python3-core needed by dnf-2.7.5-r0.corei7_64
 Problem 2: conflicting requests
  - nothing provides python3-core needed by rpm-1:4.14.2-r0.corei7_64

In this case, Python 3 is in my image because I have
package-management on, which needs Python 3.

Ross
On Wed, 17 Oct 2018 at 10:43, Burton, Ross <ross.burton@intel.com> wrote:
>
> Easiest way to determine what is pulling it in is to try removing the
> package on the target using the package manager.  That will tell you
> what dependencies are keeping it in.
>
> Ross
> On Wed, 17 Oct 2018 at 08:32, Marwen BRIKCHA <marwen.brikcha@gmail.com> wrote:
> >
> > Yes. I've seen compilation log and it does do_install in final image.
> > It's installed in /usr/lib64/python3.5 on RootFS.
> >
> > Le mer. 17 oct. 2018, à 00 h 48, Burton, Ross <ross.burton@intel.com> a écrit :
> >>
> >> On Tue, 16 Oct 2018 at 14:06, Marwen BRIKCHA <marwen.brikcha@gmail.com> wrote:
> >> >
> >> > because, when i run :
> >> > :
> >> > $> bitbake -v opencv
> >> > I can see that python3 is fetched, configure, ... etc
> >> > So, i think it the responsible for this.
> >>
> >> Please remember to CC the list.
> >>
> >> Python being built doesn't lead to Python being installed in the
> >> image.  Have a look at the image manifest (in deploy/images) or look
> >> at what is actually installed inside the image.
> >>
> >> Ross