Humberto,
The master branch of yocto-autobuilder has changed since you did this diff.
I would suggest you rebase and resubmit this particular patch.
-Bill
On Thu, Sep 1, 2016 at 12:39 PM, Humberto Ibarra <
humberto.ibarra.lo...@intel.com> wrote:
> oe-selftest is changing syntax with YOCTO #
oe-selftest is changing syntax with YOCTO #8938. This patch checks the correct
syntax version and uses the right command to avoid breaking oe-seltest
autobuilder. Should be integrated together with the syntax changing patch.
[YOCTO #8938]
Signed-off-by: Humberto Ibarra
---
.../autobuilder/bui
oe-selftest is changing syntax with YOCTO #8938. This patch checks the correct
syntax version and uses the right command to avoid breaking oe-seltest
autobuilder. Should be integrated together with the syntax changing patch.
[YOCTO #8938]
Signed-off-by: Humberto Ibarra
---
.../autobuilder/bui
Hi Humberto,
I acked the patch only a few comments, you forget to sign your patch,
please do with git commit -s.
Only for be clear this patch will support the next oe-selftest cmdline
also the old one so it could be integrated without the integration of
the oe-selttest new cmdline patch.
Cheers,
oe-selftest is changing syntax with YOCTO #8938. This patch checks the correct
syntax version and uses the right command to avoid breaking oe-seltest
autobuilder. Should be integrated together with the syntax changing patch.
[YOCTO #8938]
---
.../autobuilder/buildsteps/RunOeSelftest.py
I am trying to show a specific splash screen based on a setting.
Right now I have this in my psplash_git.bbappend
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SPLASH_IMAGES = "file://logo1.png;outsuffix=One \
file://logo2.png;outsuffix=Two"
1) I can only show one image at the moment but only
On September 1, 2016 11:54:30 AM Daniel. wrote:
> Hi Paul, Bruce
>
> Thanks for the replies,
>
> Paul,
>
> I take a look at the documentation. It's an amazing feature I'll try
> it as soon as got time avaible.
> My next question is about that "master image" that is installed at
> target hardware
On Thu, Sep 1, 2016 at 5:45 PM, Pietro wrote:
> Herman van Hazendonk
> writes:
>
>> If it takes the wrong version, it could be your layers aren't in the
>> right order. That's the first thing to check.
>>
>> You might want to try to run bitbake with
>>
>> -f protobuf -c cleanall or -f protobuf-na
Herman van Hazendonk
writes:
> If it takes the wrong version, it could be your layers aren't in the
> right order. That's the first thing to check.
>
> You might want to try to run bitbake with
>
> -f protobuf -c cleanall or -f protobuf-native -c cleanall
>
> This will remove all locally ;)
>
> T
Hi Paul, Bruce
Thanks for the replies,
Paul,
I take a look at the documentation. It's an amazing feature I'll try
it as soon as got time avaible.
My next question is about that "master image" that is installed at
target hardware so that the image
is deployed automagically. I read that it writes
If it takes the wrong version, it could be your layers aren't in the
right order. That's the first thing to check.
You might want to try to run bitbake with
-f protobuf -c cleanall or -f protobuf-native -c cleanall
This will remove all locally ;)
Then rebuild it... I haven't played much with
Herman van Hazendonk
writes:
> Hi Pietro,
>
> You shouldn't need to specify a version. DEPENDS = "protobuf" or
> DEPENDS = "protobuf-native" should do :)
>
> Herrie
>
>
>
Indeed my recipe gets built first and I can see do_protobuf_3.0.0[..](),
nonetheless when my package, which depends on libpro
Hi Pietro,
You shouldn't need to specify a version. DEPENDS = "protobuf" or DEPENDS
= "protobuf-native" should do :)
Herrie
On 2016-09-01 15:40, Pietro wrote:
Pietro writes:
Jussi Kukkonen
writes:
On 1 September 2016 at 13:21, Herman van Hazendonk
wrote:
Hi Pietro,
You can
Pietro writes:
> Jussi Kukkonen
> writes:
>
>> On 1 September 2016 at 13:21, Herman van Hazendonk
>> wrote:
>>
>> Hi Pietro,
>>
>> You can override the recipe by adding a recipe for version 3.0.0+
>> in your own layer and making sure your layer has a higher priority
>> in b
Jussi Kukkonen
writes:
> On 1 September 2016 at 13:21, Herman van Hazendonk
> wrote:
>
> Hi Pietro,
>
> You can override the recipe by adding a recipe for version 3.0.0+
> in your own layer and making sure your layer has a higher priority
> in bblayers.conf. See for example
2016-09-01 12:34 GMT+02:00 Jussi Kukkonen :
> On 1 September 2016 at 13:21, Herman van Hazendonk wrote:
>>
>> Hi Pietro,
>>
>> You can override the recipe by adding a recipe for version 3.0.0+ in your
>> own layer and making sure your layer has a higher priority in bblayers.conf.
>> See for exampl
On 1 September 2016 at 12:34, Pietro wrote:
> Maciej Borzęcki
> writes:
>
> > On Thu, Sep 1, 2016 at 10:40 AM, Pietro wrote:
> >> Maciej Borzęcki
> >> writes:
> >>
> >>> On Wed, Aug 31, 2016 at 6:44 PM, Pietro
> wrote:
> Hi all,
>
> I am new to the Yocto building system and I c
On 1 September 2016 at 13:21, Herman van Hazendonk wrote:
> Hi Pietro,
>
> You can override the recipe by adding a recipe for version 3.0.0+ in your
> own layer and making sure your layer has a higher priority in
> bblayers.conf. See for example what we do in our project:
>
> https://github.com/w
Hi Pietro,
You can override the recipe by adding a recipe for version 3.0.0+ in
your own layer and making sure your layer has a higher priority in
bblayers.conf. See for example what we do in our project:
https://github.com/webOS-ports/webos-ports-setup/blob/testing/conf/bblayers.conf
openem
Maciej Borzęcki
writes:
> On Thu, Sep 1, 2016 at 10:40 AM, Pietro wrote:
>> Maciej Borzęcki
>> writes:
>>
>>> On Wed, Aug 31, 2016 at 6:44 PM, Pietro wrote:
Hi all,
I am new to the Yocto building system and I could be talking nonsense. I
used to work with buildroot time ago
Hi Federico,
On 14/01/2016 13:37, Federico Pietro Briata wrote:
> Hi,
>
> I'm on 1.6.2 (daisy Branch), so probably I've to cherry-pick something
> more on poky.
>
> With poky-daisy-11.0.2 (Hash: e3dd621197548b4cf64988e757e9bc926082db73)
> I confirm that openjdk 7 was working for sure with this
On Thu, Sep 1, 2016 at 10:40 AM, Pietro wrote:
> Maciej Borzęcki
> writes:
>
>> On Wed, Aug 31, 2016 at 6:44 PM, Pietro wrote:
>>> Hi all,
>>>
>>> I am new to the Yocto building system and I could be talking nonsense. I
>>> used to work with buildroot time ago and I remember there is an area
>>>
Maciej Borzęcki
writes:
> On Wed, Aug 31, 2016 at 6:44 PM, Pietro wrote:
>> Hi all,
>>
>> I am new to the Yocto building system and I could be talking nonsense. I
>> used to work with buildroot time ago and I remember there is an area
>> where compiled software/packages/tools previously built ar
On Wed, Aug 31, 2016 at 6:44 PM, Pietro wrote:
> Hi all,
>
> I am new to the Yocto building system and I could be talking nonsense. I
> used to work with buildroot time ago and I remember there is an area
> where compiled software/packages/tools previously built are "staged" and
> used when buildi
24 matches
Mail list logo
