For newly added layers it may not be immediately obvious that you have
to wait for it to be indexed (since the update script is usually run on
a scheduled basis). If the layer branch hasn't been indexed, add a note
mentioning this.
Signed-off-by: Paul Eggleton
---
templates/layerindex/detail.htm
It's really irritating to be forced to specify a value for this field
especially as it'll get auto-populated by the update script. Set
blank=True to allow that. While we're at it, touch up the description a
bit to make more sense.
Signed-off-by: Paul Eggleton
---
layerindex/migrations/0009_layer
If you're diagnosing problems with the bitbake server when running the
update script, then you need to be able to look at
bitbake-cookerdaemon.log, but you couldn't do that after the fact
because the temporary directory it gets written out to was being
unconditionally deleted. Add a --keep-temp opt
This avoids the following error with GCC 7:
In file included from /usr/include/bits/getopt_posix.h:27:0,
from /usr/include/unistd.h:872,
from src/libs/libgroff/maxfilename.cc:28:
/usr/include/bits/getopt_core.h:91:12: error: declaration of 'int
getopt(in
This avoids the following error:
src/devices/grohtml/post-html.cc: In member function 'void
header_desc::write_headings(FILE*, int)':
src/devices/grohtml/post-html.cc:1402:32: error: format not a string
literal and no format arguments [-Werror=format-security]
fprintf(f, buffer.conte
On 10/03/2017 09:42 AM, Joshua Lock wrote:
Hi Jose,
Where will the previous log come from in standard QA use?
I'm wondering if we should work towards (in the 2.5 cycle) another git
repo in the yp-qa-* namespace to keep historical ptest results and
build some tooling around that, in a similar
Is there anyone that has any experience with trying to create a recipe with
devtool with the source in a mercurial repository?
I did some more searching and it looks like the 'module' is the repository that
you are trying to pull, so I modified the command to:
devtool add canfestival sources
Hi Paul,
Thanks for the corrections. I was working from examples from the book "Embedded
Linux Systems with the Yocto Project" by Rudolf J. Streif and he left out the
${PN} in the file name. Including that makes sense now that I see your
suggestions. It's now working correctly.
Thanks again,
On 3 October 2017 at 16:36, eliya@gmail.com wrote:
> Thanks Ross,
> That is the issue : default pkg-config does not search host paths - How to
> edit its search paths ?
>
"If you *really* want to link against host binaries and not building your
own native recipes for it then see qemu.inc for
Thanks Ross,
That is the issue : default pkg-config does not search host paths - How to
edit its search paths ?
On Tue, Oct 3, 2017 at 6:28 PM, Burton, Ross wrote:
> Ah, so if you're inheriting native then the default pkg-config is good,
> but the host paths are not searched out of the box.
>
>
Is this an evolution of the change in 6/8? Can it be squashed in with
that patch?
Thanks,
Joshua
On 29/09/17 03:09, Jiwei Sun wrote:
Signed-off-by: Jiwei Sun
---
tests/data/reference.xml | 3 ++-
tests/utils.c| 4 ++--
utils.c | 49 +
On 29/09/17 03:09, Jiwei Sun wrote:
* Introduce a maximum number of concurrent ptests, since
we are dealing with embedded targets.
This piece seems like it should be squashed into "[ptest-runner 5/8] Add
parallelism to TC execution"
There's a lot of code moved around and whitespace changes
Thanks for the patch, could you help potential reviewers to understand
what the patch adds and why by improving the commit message?
There's a lot of noise in this patch with unrelated whitespace changes
and formatting changes. Please re-send without those changes. Existing
coding style should
Can you add a commit message detailing what changed and why? Most of the
commit messages in this series don't help me understand what changed and
why: https://chris.beams.io/posts/git-commit/
This is especially important as the original author of the code has
moved on from the project.
On 29
Ah, so if you're inheriting native then the default pkg-config is good, but
the host paths are not searched out of the box.
If you *really* want to link against host binaries and not building your
own native recipes for it then see qemu.inc for an example of how to steal
the host pkg-config path a
Attendees: Stephen, Armin, Stephano, Saul, Mark, Michael, Joshua, Robin, Brian,
Ulf
Agenda:
* Opens collection - 5 min (Stephen)
* Yocto Project status - 5 min (Stephen/team)
YP 2.2.2 was released.
YP 2.3.2 was released.
YP 2.4 M4 is in QA and 81% complete. See status at:
https://wiki.yoctopro
when running the recipe I get during do_configure:
Checking for header stdlib.h : yes
...
Checking for program pkg-config :
/home/wzbwjj/vpm/GR_Yocto/build/tmp/sysroots/x86_64-linux/usr/bin/pkg-config
How do I change that ?
On Tue, Oct 3, 2017 at 6:02 PM, Burton, Ross wrote
You don't need to, it will search the host.
Ross
On 3 October 2017 at 15:54, eliya@gmail.com wrote:
> Hi Ross,
> how to configure use of pkg-config-native ?
>
> On Tue, Oct 3, 2017 at 5:51 PM, Burton, Ross
> wrote:
>
>> On 3 October 2017 at 15:13, eliya@gmail.com
>> wrote:
>>
>>> Hi a
Hi Ross,
how to configure use of pkg-config-native ?
On Tue, Oct 3, 2017 at 5:51 PM, Burton, Ross wrote:
> On 3 October 2017 at 15:13, eliya@gmail.com
> wrote:
>
>> Hi all,
>> I am new to the Yocto project.
>> Is this the Yocto forum ?
>> I would like configure pkg-config search directories
On 3 October 2017 at 15:13, eliya@gmail.com wrote:
> Hi all,
> I am new to the Yocto project.
> Is this the Yocto forum ?
> I would like configure pkg-config search directories but, the program
> configured from the sysroots file system, so it does not see Host
> environment variables.
> i.e
Hi Jose,
Where will the previous log come from in standard QA use?
I'm wondering if we should work towards (in the 2.5 cycle) another git
repo in the yp-qa-* namespace to keep historical ptest results and build
some tooling around that, in a similar vein to poky-buildhistory /
buildhistory-di
Hi all,
I am new to the Yocto project.
Is this the Yocto forum ?
I would like configure pkg-config search directories but, the program
configured from the sysroots file system, so it does not see Host
environment variables.
i.e : there are two pkg-config apps : Host's pkg-config located at
/usr/bin
ouch...this was clearly wrong
opkg-utils is badly needing an ATS to prevent this bugs from slipping in...
thanks a bunch for the fix! (just merged it into master)
On 10/02/2017 02:37 PM, Jeffrey Pautler wrote:
Signed-off-by: Jeffrey Pautler
---
opkg.py | 2 +-
1 file changed, 1 insertion(+
23 matches
Mail list logo
