Thank you for the clarification that helps
BR
Måns Zigher
Den ons 17 okt. 2018 kl 00:36 skrev Andre McCurdy :
> On Tue, Oct 16, 2018 at 6:47 AM, Burton, Ross
> wrote:
> > It's only already-stripped that needs to be on PN, because the
> > stripping happens before packaging. When
On Tue, 16 Oct 2018 at 14:06, Marwen BRIKCHA 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
On Tue, Oct 16, 2018 at 6:47 AM, Burton, Ross wrote:
> It's only already-stripped that needs to be on PN, because the
> stripping happens before packaging. When already-stripped files,
> there are no packages yet.
>
> Ross
> On Tue, 16 Oct 2018 at 14:22, Måns Zigher wrote:
>>
>> Ok so it is not
We are pleased to announce the third milestone release for Yocto Project 2.6
(yocto-2.6_M3) is available for download now.
Download:
http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-2.6_M3/
bitbake e72be96cfa9f05fda5f420c7cfa8bcfa9304b884
eclipse-poky-neon
We are pleased to announce the third milestone release for Yocto Project 2.6
(yocto-2.6_M3) is available for download now.
Download:
http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-2.6_M3/
bitbake e72be96cfa9f05fda5f420c7cfa8bcfa9304b884
eclipse-poky-neon
On Tue, Oct 16, 2018 at 03:46:25PM +0100, Burton, Ross wrote:
This is simply because you can't patch a bbclass. You'll have to copy
it into your layer with the modification, or work upstream to get a
suitable change merged.
What I've done in this situation is add a new layer
(poky-patches),
Current Dev Position: YP 2.6 M4.
Next Deadline: YP 2.6 M4 Build Target was Oct. 1, 2018
SWAT Team Rotation:
· SWAT lead is currently: Ross
· SWAT team rotation: Ross -> Amanda on Oct. 17, 2018
· SWAT team rotation: Amanda -> Tracy on Oct. 24, 2018
·
This is simply because you can't patch a bbclass. You'll have to copy
it into your layer with the modification, or work upstream to get a
suitable change merged.
Ross
On Tue, 16 Oct 2018 at 15:45, Richard Collins
wrote:
>
> I have integrated mender into our system and now everything is working.
I have integrated mender into our system and now everything is working. I
had to change one of the mender class files. Just a one line change in a
function. As we'll be using automated build servers soon I need this change
to be permanent.
I've created a patch file in our bsp layer of the same
Yes, I want to source the data files. I'm trying to adapt devtool the way
it's creating the workspace, then I'm sourcing a script with all the
necessary variables and then interactively run commands by hand.
I was thinking about the devshell but in devshell variables like ${S}, ${B}
are not set
It's only already-stripped that needs to be on PN, because the
stripping happens before packaging. When already-stripped files,
there are no packages yet.
Ross
On Tue, 16 Oct 2018 at 14:22, Måns Zigher wrote:
>
> Ok so it is not supported to have the already-stripped on a package level? I
>
I've meta-intel and poky. I'm not sure which layer it's in, as an attempt to
find/grep files with ixgbe in the recipes directories doesn't turn up anything.
The source seems to be downloaded to work-shared sub-directory during the
bitbake process.
The .ko file is located in the following
Ok so it is not supported to have the already-stripped on a package level?
I cannot set it on PN because I have some so-files that is already stripped
and others that is not so that was why I wanted to create a package for the
already-stripped so-files and use the already-stripped on that package.
Do you actually want to source the data files, and if so why? As with
the bitbake -e output, it's shell-like but not actually shell.
Ross
On Tue, 16 Oct 2018 at 13:44, Tomasz Dziendzielski
wrote:
>
> Hi,
> when using archiver.bbclass the do_dumpdata task is using bb.data.emit_env
> function,
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 wrote:
>
> Hello Ross,
>
> I've set in my receipe opencv_3.%.bappend
> PACKAGECONFIG = "eigen jpeg png tiff v4l libv4l gstreamer"
> EXTRA_OECMAKE_append = " \
>
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
Hi,
when using archiver.bbclass the do_dumpdata task is using bb.data.emit_env
function, which should emit variables "in a format such that it can be
sourced by a shell.".
The problem is that the *-showdata.dump file can't be properly sourced,
because variables are not in a correct format.
There
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 wrote:
>
> Hello,
>
> I'm using Yocto Poky 2.4.1 and bitbake version 1.6.0 to build a xilinx
>
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
--
19 matches
Mail list logo
