Re: [yocto] Yocto 2.7 SDK Eclipse

[Bert Böhne]

Hi Alex,

thanks for your reply. Do I need the plugins for writing and debugging code in 
Eclipse? The documentation says:

24.9.11. ADT Removed¶

The Application Development Toolkit (ADT) has been removed because its 
functionality almost completely overlapped with the standard SDK and the 
extensible SDK. For information on these SDKs and how to build and use them, 
see the Yocto Project Application Development and the Extensible Software 
Development Kit (eSDK) manual.

So would it work if I use Eclipse and maybe a plugin for CMake? Start Eclipse 
from the cmdline where I sourced the SDK environment setup script?

What is the ‘normal’ way or tool for writing applications? Is it weird to want 
to use Eclipse?

Thanks,

Bert

Von: Alexander Kanavin [mailto:alex.kana...@gmail.com]
Gesendet: Dienstag, 20. August 2019 17:42
An: Bert Böhne 
Cc: yocto@yoctoproject.org
Betreff: Re: [yocto] Yocto 2.7 SDK Eclipse

On Tue, 20 Aug 2019 at 17:34, Bert Böhne 
mailto:bert.boe...@systec.de>> wrote:
I am using Yocto 2.7 and I want to use the SDK to build applications(or give 
the SDK to my colleagues to let them build applications). I have read in the 
documentation that there are plugins for Eclipse. But for Yocto 2.7(or maybe 
earlier) the support for this plugin was removed. So if we want to use Eclipse 
(and CMake), is this still possible? I am a little confused about this.

If anybody could give me a hint, I would appreciate it very much.

It is possible, but you have to maintain it. The project couldn't find anyone 
to take care of the plugins, and so the only remaining option was to disable 
them.

Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Building SDK for macOS

[Andy Pont]

Ross wrote...


Did a little poking.

The need to build a SDK tarball on an existing macOS could probably be removed 
by using one of the convenient tarballs from 
https://github.com/phracker/MacOSX-SDKs/releases.

The SDK is 32-bit, which is going to be an issue on modern macOS systems.

The layer has several versioned bbappends which need updating to work with 
recent releases.

None of this is insurmountable, meta-darwin has been used for products in the 
past and with a little effort can be made to do so again.
Thanks for the feedback. If time allows I may take a look into some of 
these issues and see if they are resolvable. In the meantime, I think a 
headless Linux VM with SSH and NFS support enabled might be the quicker 
route to follow.


-Andy.



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Final DISTRO_FEATURES value

[Mauro Ziliani]

Thanks

I try

Il 21/08/19 08:36, Gabriele Zampieri ha scritto:
> Ciao,
>
> you can inspect the testdata file located next to the generated image,
> under deploy floder.
>
> Best regards,
> Gabriele
>
> Il giorno mer 21 ago 2019 alle ore 08:25 Mauro Ziliani
> mailto:ma...@faresoftware.it>> ha scritto:
>
> Hi all.
>
> How can I inspect the final value of DISTRO_FEATURES when bitbake has
> completed the parse all recipes?
>
>
> Best regards,
>
>    MZ
>
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org 
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] libGL missing. Which packages bring it?

[Mauro Ziliani]

Hi all

I try to compile kivy for Pyro and Python3 for framebuffer con RPi3.

The builder cannot find libGL and -lGL linker fails.

Which are the packages that give libGL?


Best regards

    Mauro

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto 2.7 SDK Eclipse

[Alexander Kanavin]

On Wed, 21 Aug 2019 at 11:00, Bert Böhne  wrote:

> thanks for your reply. Do I need the plugins for writing and debugging
> code in Eclipse? The documentation says:
>
>
>
> 24.9.11. ADT Removed¶
>
>
>
> The Application Development Toolkit (ADT) has been removed because its
> functionality almost completely overlapped with the standard SDK and the
> extensible SDK. For information on these SDKs and how to build and use
> them, see the Yocto Project Application Development and the Extensible
> Software Development Kit (eSDK) manual.
>
>
>
> So would it work if I use Eclipse and maybe a plugin for CMake? Start
> Eclipse from the cmdline where I sourced the SDK environment setup script?
>
>
>
> What is the ‘normal’ way or tool for writing applications? Is it weird to
> want to use Eclipse?
>

I do not want to define 'normal'; for me personally the way to work is to
do everything from command line, with an extremely lightweight editor (e.g.
nano). Since I have never used Eclipse, I do not know what the (now
removed) plugins actually do. You can certainly still edit code using
Eclipse but I can imagine that for building it, and running it and other
things you would have to switch to the command line.

Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to override RRECOMMENDS

[Matthias Schoepfer]

Hi!

In my update to latest warrior, I came across 
4b393a21ffcf9fe00577b4a46c38b5db89b39e9d, which adds rng-tools as 
RRECOMMENDS. So far, so good. But for some reason, rng-tools fails 
miserably on my platform, why I cannot say, because it blocks the 
watchdog daemon, so before I can get logged in, a reboot happens.


So I go and read the manual, and come across PACKAGE_EXCLUDE, 
NO_RECOMMENDATIONS and BAD_RECOMMENDATIONS. I tried all of them from 
local.conf:



PACKAGE_EXCLUDE = "rng-tools"


NO_RECOMMENDATIONS =  "1"


BAD_RECOMMENDATIONS = "rng-tools"

and even with the pn-target_image/||/ (and yes, I replaced target_image 
with my image name). But nothings seems to help. What am I missing?


Regards,

    Matthias


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [psplash][PATCH] bmp: Add option to print bmp image

[Mickaël Tansorier]

Add option to load image in `psplash` command line.
Image is bmp3 format. If this image can not be found or
loading fail, default image is print.

bmp_layout.h: describe bmp3 file inspire of bmp_layout.h
from u-boot.
psplash-fb.{c|h}: add function to draw GBR888 image.
psplash.c: Add option to read bmp image and print it
if loading file is right.

Signed-off-by: Mickaël Tansorier 
---
 bmp_layout.h | 35 +++
 psplash-fb.c | 25 ++
 psplash-fb.h |  9 +
 psplash.c| 95 ++--
 4 files changed, 161 insertions(+), 3 deletions(-)
 create mode 100644 bmp_layout.h

diff --git a/bmp_layout.h b/bmp_layout.h
new file mode 100644
index 000..f397ef9
--- /dev/null
+++ b/bmp_layout.h
@@ -0,0 +1,35 @@
+/* Layout of a bmp file */
+/* format = bmp3*/
+
+#ifndef _BMP_LAYOUT_H_
+#define _BMP_LAYOUT_H_
+
+#define BMP_IMG_BYTES_PER_PIXEL 3
+
+struct __attribute__((__packed__)) bmp_header {
+   /* Header */
+   char signature[2];
+   __u32   file_size;
+   __u32   reserved;
+   __u32   data_offset;
+   /* InfoHeader */
+   __u32   size;
+   __u32   width;
+   __u32   height;
+   __u16   planes;
+   __u16   bit_count;
+   __u32   compression;
+   __u32   image_size;
+   __u32   x_pixels_per_m;
+   __u32   y_pixels_per_m;
+   __u32   colors_used;
+   __u32   colors_important;
+};
+
+struct bmp_image {
+   struct bmp_header header;
+   /* ColorTable */
+   uint8 * data;
+};
+
+#endif /* _BMP_LAYOUT_H_ */
diff --git a/psplash-fb.c b/psplash-fb.c
index c064d18..307d6a8 100644
--- a/psplash-fb.c
+++ b/psplash-fb.c
@@ -441,6 +441,31 @@ psplash_fb_draw_image (PSplashFB*fb,
 }
 }
 
+void
+psplash_fb_draw_image_raw_GBR888 (PSplashFB*fb,
+  int  x,
+  int  y,
+  int  img_width,
+  int  img_height,
+  int  img_bytes_per_pixel,
+  uint8   *rle_data)
+{
+  uint8   *p = rle_data;
+  int  dx = 0, dy = 0,  total_len;
+  int  img_rowstride = img_bytes_per_pixel*img_width;
+
+  total_len = img_rowstride * img_height;
+  /* Start at the end of pointer */
+  p += (total_len - 1);
+
+  while ((p - rle_data) >= 0)
+{
+   psplash_fb_plot_pixel (fb, x-dx, y+dy, *(p), *(p-1), *(p-2));
+   if (++dx * img_bytes_per_pixel >= img_rowstride) { dx=0; dy++; }
+   p -= img_bytes_per_pixel;
+}
+}
+
 /* Font rendering code based on BOGL by Ben Pfaff */
 
 static int
diff --git a/psplash-fb.h b/psplash-fb.h
index d0dce10..297add8 100644
--- a/psplash-fb.h
+++ b/psplash-fb.h
@@ -77,6 +77,15 @@ psplash_fb_draw_image (PSplashFB*fb,
   int  img_rowstride,
   uint8   *rle_data);
 
+void
+psplash_fb_draw_image_raw_GBR888 (PSplashFB*fb,
+  int  x,
+  int  y,
+  int  img_width,
+  int  img_height,
+  int  img_bytes_pre_pixel,
+  uint8   *rle_data);
+
 void
 psplash_fb_text_size (int*width,
  int*height,
diff --git a/psplash.c b/psplash.c
index 992e199..f8a92b6 100644
--- a/psplash.c
+++ b/psplash.c
@@ -24,6 +24,7 @@
 #include "psplash-poky-img.h"
 #include "psplash-bar-img.h"
 #include "radeon-font.h"
+#include "bmp_layout.h"
 
 #define SPLIT_LINE_POS(fb)  \
(  (fb)->height \
@@ -40,6 +41,59 @@ psplash_exit (int UNUSED(signum))
   psplash_console_reset ();
 }
 
+struct bmp_image *read_image_bmp(char *image_name)
+{
+  FILE *file;
+  size_t read;
+  struct bmp_image *bmp;
+
+  file = fopen(image_name, "rb");
+  if (file != NULL)
+{
+  bmp = malloc(sizeof(struct bmp_image));
+
+  /* Read header */
+  read = fread(&bmp->header, sizeof(struct bmp_header), 1, file);
+  if (read != 1)
+{
+  printf("Error: Fail to read header\n");
+  free(bmp);
+  fclose(file);
+  return NULL;
+}
+
+  /* Read BMP image signature */
+  if (bmp->header.signature[0] != 'B' && bmp->header.signature[1] != 'M')
+{
+  printf("Error: File format is not correct.\n");
+  free(bmp);
+  fclose(file);
+  return NULL;
+}
+
+  bmp->data = malloc(sizeof(uint8) * bmp->header.image_size);
+
+  /* Read data image */
+  read = fread(bmp->data, sizeof(uint8), (bmp->header.image_size), file);
+  if (read != bmp->header.image_size)
+{
+  printf("Error: Cannot read data image.\n");
+  free(bmp);
+  fclose(file);
+  return NULL;
+}
+
+  fclose(file);
+}
+  else
+{
+  

Re: [yocto] Yocto 2.7 SDK Eclipse

[Bert Böhne]

OK, thanks. We would like to use Eclipse because we are coming from Windows and 
it would give us the possibility to code and debug easier or in a more known 
way.

Von: Alexander Kanavin [mailto:alex.kana...@gmail.com]
Gesendet: Mittwoch, 21. August 2019 12:03
An: Bert Böhne 
Cc: yocto@yoctoproject.org
Betreff: Re: [yocto] Yocto 2.7 SDK Eclipse

On Wed, 21 Aug 2019 at 11:00, Bert Böhne 
mailto:bert.boe...@systec.de>> wrote:
thanks for your reply. Do I need the plugins for writing and debugging code in 
Eclipse? The documentation says:

24.9.11. ADT Removed¶

The Application Development Toolkit (ADT) has been removed because its 
functionality almost completely overlapped with the standard SDK and the 
extensible SDK. For information on these SDKs and how to build and use them, 
see the Yocto Project Application Development and the Extensible Software 
Development Kit (eSDK) manual.

So would it work if I use Eclipse and maybe a plugin for CMake? Start Eclipse 
from the cmdline where I sourced the SDK environment setup script?

What is the ‘normal’ way or tool for writing applications? Is it weird to want 
to use Eclipse?

I do not want to define 'normal'; for me personally the way to work is to do 
everything from command line, with an extremely lightweight editor (e.g. nano). 
Since I have never used Eclipse, I do not know what the (now removed) plugins 
actually do. You can certainly still edit code using Eclipse but I can imagine 
that for building it, and running it and other things you would have to switch 
to the command line.

Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] npm nodejs

[Jonas Andersson]

Hi

I have used Yocto and npm/nodejs now for about 1 year and think it works
but I not without some extra work. Are there any group working on
npm/nodejs? As I use it quite frequent and puts some extra work every time
i create an recipe I have some interest in supporting the work on
npm/nodejs to make it an better experience.

I thinks It quite hard to follow all the npm/nodejs parts of Yocto(devtool,
fetcher and meta-oe/../nodejs), I get the feeling that all parts not are in
sync.

I am no python developer but I would be happy to support and discuss
solutions and questions regarding Yocto and npm/nodejs.

Regards
Jonas
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Recipe svn-fetcher and scmdata

[Richard Purdie]

On Mon, 2019-08-19 at 10:18 +0300, Teemu K wrote:
> Hi,
> 
> I have some recipes that fetch sources directly from svn. I'd like to
> keep the .svn to make it easier to commit changes. I checked that
> those are by default removed and that there is scmdata - option if
> those wanted to be kept.
> 
> I set the following src_uri:
> 
> SRC_URI =
> "svn://my.svn.server/svn/sw_components/program/;module=trunk;protocol
> =http;scmdata=keep"
> 
> Yet the .svn - data is removed from the sources under build -
> directory. It is in under download directory though so I'm wondering
> if I got this right in the first place?
> 
> I tried with devtool modify and it seems I ended up having .git -
> directory there although sources are in svn. Maybe it's systems
> 'subtle' way of telling me to switch to git? ;)
> 
> But should the scmdata=keep option work like I'm thinking it should
> and/or what I'm doing wrong?

I have a suspicion the build directory (${B}) may be getting cleaned by
one of the tasks and wiping out the scm data but its just a guess...

Cheers,

Richard

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] npm nodejs

[Stefan Herbrechtsmeier]

Hi Jonas,

Am 21.08.19 um 14:55 schrieb Jonas Andersson:
I have used Yocto and npm/nodejs now for about 1 year and think it works 
but I not without some extra work. Are there any group working on 
npm/nodejs? As I use it quite frequent and puts some extra work every 
time i create an recipe I have some interest in supporting the work on 
npm/nodejs to make it an better experience.


I thinks It quite hard to follow all the npm/nodejs parts of 
Yocto(devtool, fetcher and meta-oe/../nodejs), I get the feeling that 
all parts not are in sync.


I have start reworking the nodejs support but haven't the time to finish it.

I have remove the use of the bitbake npm fetcher. I create a recipe per 
npm package major version. Thereby the recipe downloads the npm archive 
via https, extract it to /usr/lib/node_modules/name-major and creates 
links for the dependency packages and binaries. This avoids duplicated 
npm packages and allows a per package optimization like the remove of 
scripts, tests and documentations. Furthermore I can patch npm packages 
to use dynamic linking or build native packages.


I have add a new plugin to the recipetool which creates a recipe from a 
npm package. It extract the license, dependencies and binaries from the 
package.json. Thereby the dependencies string is parsed and translated 
into a - or -0.version> if major version is below 0. I assume that I can ignore the 
minor and patch version number and always use the latest compatible version.


On top of recipetool I have a script with creates a recipe for a npm 
package and all its dependencies.



Regards
  Stefan
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto