set in the ramdisk node the compression property
always to "none", as U-Boot nowadays since commit:
b1307f884a91 ("fit: Support compression for non-kernel components (e.g. FDT)")
decompress non kernel components. Setting compression
to the used comression algorithm now, will end in
fail of your k
This should go to the oe-core list,
openembedded-c...@lists.openembedded.org.
Thanks,
Ross
On 19/09/2019 09:13, Heiko Schocher wrote:
set in the ramdisk node the compression property
always to "none", as U-Boot nowadays since commit:
b1307f884a91 ("fit: Support compression for non-kernel comp
I have a set of data files (cryptographic keys) that I would like to
share among several recipes in my build. They won't go into the
rootfs, but they will be used by multiple recipes that construct the
rootfs. So, to the best of my understanding, it seems like I should
put them in sysroot and som
On Thu, Sep 19, 2019 at 09:39:32AM -0400, Patrick Doyle wrote:
> I have a set of data files (cryptographic keys) that I would like to
> share among several recipes in my build. They won't go into the
> rootfs, but they will be used by multiple recipes that construct the
> rootfs. So, to the best
On 9/19/19 2:56 AM, Robert ber...@yocto.user wrote:
Hi,
Does someone happen to have a BitBake recipe for gitlab-runner?[1]
[1] https://gitlab.com/gitlab-org/gitlab-runner
A quick search did not show up anything;)
There's nothing in the layer index:
https://layers.openembedded.org/layerindex
On Thu, Sep 19, 2019 at 9:39 AM Patrick Doyle wrote:
> do_install() {
> install -d ${D}/${datadir}
> install -m 755 -d ${WORKDIR}/keys ${D}/${datadir}
> }
>
Oops... I just noticed the typo(s) in my recipe... I wasn't installing
the contents of my ${WORKDIR} in ${D}${datadir}/keys the way
On Thu, Sep 19, 2019 at 9:48 AM wrote:
> One possibility is to provide these keys as host native tools and data to
> build of target recipes. This makes the files available in the build
> environment
> but does not expose them to target.
>
> Create a -native recipe which has and installs the file
On Thu, Sep 19, 2019 at 09:39:55AM -0400, Randy MacLeod wrote:
> On 9/19/19 2:56 AM, Robert ber...@yocto.user wrote:
> > Hi,
> >
> > Does someone happen to have a BitBake recipe for gitlab-runner?[1]
> >
> > [1] https://gitlab.com/gitlab-org/gitlab-runner
> >
> > A quick search did not show up a
On 19.09.2019 15:39, Patrick Doyle wrote:
> I have a set of data files (cryptographic keys) that I would like to
> share among several recipes in my build. They won't go into the
> rootfs, but they will be used by multiple recipes that construct the
> rootfs. So, to the best of my understanding,
Hi,
based on André recommendation I commented out the PS1 variable and now I get
`-sh-4.4#` for the prompt. I also checked and nothing is overwriting the
variable.
But I tried to change the size of the shell by using `stty cols 100 rows 40` as
well as different sizes (smaller and bigger than 8
On 9/19/19 11:43 AM, phodina wrote:
Hi,
based on André recommendation I commented out the PS1 variable and now I get
`-sh-4.4#` for the prompt. I also checked and nothing is overwriting the
variable.
But I tried to change the size of the shell by using `stty cols 100 rows 40` as
well as diff
How about using `tput smam'?
Regards,
Chen Qi
On 09/19/2019 11:43 PM, phodina wrote:
Hi,
based on André recommendation I commented out the PS1 variable and now I get
`-sh-4.4#` for the prompt. I also checked and nothing is overwriting the
variable.
But I tried to change the size of the shel
A build flagged for QA (yocto-2.8_M3.rc1) was completed on the autobuilder and
is available at:
https://autobuilder.yocto.io/pub/releases/yocto-2.8_M3.rc1
Build hash information:
bitbake: 797354d285f6d624d9adb52bab65823572da0e39
meta-gplv2: 1e2480e50f34e55bdfd5e06f98441e03a3752d5a
meta
Hi,
Please see my comments in-line.
On 19/09/2019 15:48, Simon Spannagel wrote:
Hi all,
the linked layer does not provide a bitbake recipe for the gitlab-runner
to be built but only some instructions of how to set up a runner
instance to run bitbake on. Was this what you were looking for?
Ac
Hi Yann,
Please se my comments in-line
On 19/09/2019 16:35, Yann Dirson wrote:
Do you want a recipe for gitlab-runner, or something for getting
gitlab-runned to tun a bitbake build ? The latter I have, though
imperfect and not readily packaged, but I can possibly try to publish
something (plan
Hello All,
I have a feeling that the empty packages are really not useful inside
rootfs/sysroot either dependency with other packages, isn't it?
Is there already a way in Yocto to remove/avoid empty packages from rootfs?
PACKAGE_EXCLUDE would do that, but looking for a better option which can
Hi,
Is your problem of line wrapping only on the serial console, or also on
an ssh session?
Which version of Yocto do you use?
systemd or sys-v?
Regards,
Robert
On 19/09/2019 17:43, phodina wrote:
Hi,
based on André recommendation I commented out the PS1 variable and now I get
`-sh-4.4#
17 matches
Mail list logo
