I have a recipe that builds an application from the master branch of a local git repository. AUTOREV is working, so the recipe automatically rebuilds whenever the repository is updated. The source cod

#yocto #python

https://www.yoctoproject.org/docs/3.0/ref-manual/ref-manual.html#var-AUTOREV https://www.yoctoproject.org/docs/3.0/ref-manual/ref-manual.html#var-SRCPV

#yocto #python

Adding a native package into a target image does not make sense. What are you trying to achieve? - Jussi

#yocto #python

Sorry Khem, With esc character '\' before & it can't take the full path. So briefly: Yocto build with char '\' before & in SRC_URI: online - OK offline - Error - svn: E170013: Unable to connect to a r

#yocto #python

Hi Khem, Yes, no issues with that. When I am connected to network it fetches the code with and without escape character before & in the path. svn co " http://cocosubversion/svn/Embedded/Valve&Actuator

#python #yocto

Looks good to me. Lucky you :) -Mikko

#yocto #python

Recipe --> python3-psycopg2-native --> https://layers.openembedded.org/layerindex/recipe/72275/ Added this recipe using `IMAGE_INSTALL` variable in `sjpl-image.bb` file Got following errors while buil

#yocto #python

Hello Community, This is the third time I am asking for support on this issue. This time I decided to use the web form. In our project we have a requirement to be able to build the project offline. E.

#yocto #python

Hi, I can't comment on svn fetcher but I use subversion via http fetcher. This way the local download cache can have the exact same file and builds can continue off line. One major gotcha is that all

#yocto #python

svn: E170013: Unable to connect to a repository at URL 'http://cocosubversion/svn/Embedded/Valve&Actuator/DVPII/trunk/SOCPACManEnvEngKeys/trunk' svn: E670003: Temporary failure in name resolution can

#yocto #python

Hello Team, I am Akhila, outreachy applicant and I'm new to opensource projects. I'm excited to contribute to yocto project. I hope you guys would help me with this.

#yocto #python

Welcome to this amazing community Akhila

#yocto #python

Hi, I would like to work on #10699 -- Ensure consistency in repository URLs bug. Kindly help me to move forward by providing more information on this issue(like where I can find more URL's mentioned i

#yocto #python

Hi Akhila, This bug is about the data in the recipes in oe-core and all layers. There is a layer tracking system called 'the layer index': https://layers.openembedded.org where you can search by vario

#yocto #python

Hi folks my replies inline below Actually for this issue we're not concerned with SRC_URI, just the repo URL at the layer level - the database is normalised so that the latter is mostly in one place.

#yocto #python

Hi, I am trying to compile python package for yocto and I found python3 (python3.7) is build native then it cross compiled.I want to know why it is done like this in python. Basically I want python3 b

#python

right, add BBCLASSEXTEND = "native" in lapack recipe and fix the needed bits to get it going.

#python

DEPEND on python3 and python3-native then. Ross

#python

The python3 build for target doesn't directly depend on python3-native. Some recipes do depend on python3-native (although by definition there is a python3 on your host) as they need to run non-standa

#python

Howdy! Am Fr., 6. Nov. 2020 um 09:23 Uhr schrieb <william.jacob@...>: I'm sorry, but I don't really understand the question. You say you want python3 crosscompiled. This will happen if somethi

#python