Re: [yocto] xsltproc failing to load docbook.xsl

[Colin Helliwell]

> On 03 April 2017 at 14:11 "Burton, Ross"  wrote:
> 
> On 3 April 2017 at 14:07, Colin Helliwell  
> wrote:
> 
> > Hmmm, that's not got it unfortunately.
> >  I've also added a depend on libxslt-native (to get the xsltproc binary 
> > itself), and can see docbook-xsl-stylesheets-native building first - it 
> > creates a lot of docbook.xml's in various places (e.g. down under 
> > tmp/sysroots/x86_64-linux/, and tmp/work/x86_64-linux/), but the 
> > networkmanager recipe still isn't then finding that file.
> 
> There's a few pieces in oe-core which use docbook-xsl, I'd grep it and see if 
> there are any obvious fixes required.
> 

I think I've solved this now - it appears that the necessary DEPENDS are
libxslt-native  docbook-xsl-stylesheets-native  xmlto-native
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Ad git revision to image name

[Paul Eggleton]

Hi Tobias,

On Friday, 7 April 2017 4:09:45 AM NZST Grueninger, Tobias wrote:
> I would like to automatically add the git Revison checksum to the generated
> Yocto image name, e.g. 'core-image-git_bc123456.img'

Well, the immediate question would be which git revision is this? Your custom 
layer? Poky / OE-core? The kernel?

As for the mechanism, assuming you can get the revision at parse time, it's a 
bit crude but you could do something like this:

python() {
repopath = '/path/to/git/repository'
gitver = subprocess.check_output('git rev-parse HEAD', cwd=repopath)
d.appendVar('IMAGE_BASENAME', '-git_%s' % gitver)
}

If parse time is too early you might try doing something at the start of 
do_rootfs, either a do_rootfs_prepend or a prefunc that does something similar 
to the above. In that case I'd be worried that we have other image tasks that 
look at IMAGE_BASENAME (via IMAGE_NAME) though.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] runqemu - "Could not initialize SDL(No available video device) - exiting"

[Martin Kelly]

I found the source of the issue (SDL must be compiled with X11 support) 
and sent a patch to OE-core to fix it:


https://patchwork.openembedded.org/series/6211

On 04/04/2017 03:41 PM, Martin Kelly wrote:

[This sender failed our fraud detection checks and may not be who they
appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing]

Hi,

I'm hitting an error on runqemu when I try to build an SDK and image on
one machine and run it on another, even when the build machine and
qemu-running machine match very closely (both running Debian Jessie on
Intel 64-bit hardware). Specifically, I get this error:

Could not initialize SDL(No available video device) - exiting

Interestingly, I don't get this when I do runqemu on the same machine
that built the image and SDK (in fact, it works on either machine, as
long as the image/SDK never leave the machine). Now, if I manually copy
and paste the runqemu command, but just use the Debian-provided qemu
instead of the one from the SDK, then again everything works fine. Note
also that libSDL-1.2.so.0 is installed on both systems. At this point
I'm pretty stumped.

Google says that, in the past, this occurred because of X11 ABI issues:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=5040

However, the x11-native version I'm building through 1.6.3, and Debian
Jessie provides 1.6.2, so I would guess the ABI is OK between those two
versions. In addition, the fact that it works on the same machine that
built the SDK and image is strange.

Any ideas what might be wrong?

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

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

Re: [yocto] [ptest-runner][PATCHv2 2/2] Add xml output

[Aníbal Limón]

Hi Pascal,

I did some changes to your patch, see comments inline.

As i said i plan to integrate for 2.1 version of ptest-runner.

See the branch,

http://git.yoctoproject.org/cgit/cgit.cgi/ptest-runner2/log/?h=devel

Thanks for your contribution,
Anibal

On 02/01/2017 09:42 AM, Pascal Bach wrote:
> The format follow the one defined in the Yocto wiki:
> https://wiki.yoctoproject.org/wiki/QA/xUnit_XML_Template
> 
> It is only the minimum required but it can be extended in the future.
> 
> Signed-off-by: Schuler Christian 
> Signed-off-by: Pascal Bach 
> ---
>  README.md|  1 +
>  main.c   | 13 ++---
>  tests/data/reference.xml |  8 
>  tests/utils.c| 46 
>  utils.c  | 50 
> 
>  utils.h  | 10 --
>  6 files changed, 123 insertions(+), 5 deletions(-)
>  create mode 100644 tests/data/reference.xml
> 
> diff --git a/README.md b/README.md
> index ed7a589..fedab04 100644
> --- a/README.md
> +++ b/README.md
> @@ -14,6 +14,7 @@ Now the ptest-runner2 support the next features:
>  - List available ptests.
>  - Specify the timeout for avoid blocking indefinetly.
>  - Only run certain ptests.
> +- XML-ouput
>  
>  Proposed features:
>  
> diff --git a/main.c b/main.c
> index 765d688..5f37541 100644
> --- a/main.c
> +++ b/main.c
> @@ -41,7 +41,7 @@
>  static inline void
>  print_usage(FILE *stream, char *progname)
>  {
> - fprintf(stream, "Usage: %s [-d directory] [-l list] [-t timeout] "
> + fprintf(stream, "Usage: %s [-d directory] [-l list] [-t timeout] [-x 
> xml-filename]"
>   "[-h] [ptest1 ptest2 ...]\n", progname);
>  }
>  
> @@ -60,12 +60,14 @@ main(int argc, char *argv[])
>   struct ptest_list *head, *run;
>  
>   struct options opts;
> +
>   opts.directory = strdup(DEFAULT_DIRECTORY);
>   opts.list = 0;
>   opts.timeout = DEFAULT_TIMEOUT;
>   opts.ptests = NULL;
> + opts.xml_filename = NULL;
>  
> - while ((opt = getopt(argc, argv, "d:lt:h")) != -1) {
> + while ((opt = getopt(argc, argv, "d:ltx:h")) != -1) {
>   switch (opt) {
>   case 'd':
>   free(opts.directory);
> @@ -82,6 +84,11 @@ main(int argc, char *argv[])
>   print_usage(stdout, argv[0]);
>   exit(0);
>   break;
> + case 'x':
> + free(opts.xml_filename);
> + opts.xml_filename = strdup(optarg);
> + CHECK_ALLOCATION(opts.xml_filename, 1, 1);
> + break;
>   default:
>   print_usage(stdout, argv[0]);
>   exit(1);
> @@ -125,7 +132,7 @@ main(int argc, char *argv[])
>   run = filter_ptests(head, opts.ptests, ptest_num);
>   CHECK_ALLOCATION(run, ptest_num, 1);
>   ptest_list_free_all(head);
> - } 
> + }
>  
>   rc = run_ptests(run, opts, argv[0], stdout, stderr);
>  
> diff --git a/tests/data/reference.xml b/tests/data/reference.xml
> new file mode 100644
> index 000..0d858e1
> --- /dev/null
> +++ b/tests/data/reference.xml
> @@ -0,0 +1,8 @@
> +
> +
> +
> +
> +
> +
> +
> +

The format is better to use tabs, for denote hierarchy , i changed this
part. Example:






<
/failure>




> diff --git a/tests/utils.c b/tests/utils.c
> index 6b70c2e..f5d3b62 100644
> --- a/tests/utils.c
> +++ b/tests/utils.c
> @@ -237,6 +237,50 @@ START_TEST(test_run_fail_ptest)
>   ptest_list_free_all(head);
>  END_TEST
>  
> +int filecmp(FILE *fp1, FILE *fp2)

Style:

int
filecmp(FILE *fp1, FILE *fp2)


> +{
> +char f1, f2;
> +while (1) {
> +   int end = 0;
> +if ((f1 = getc(fp1)) == EOF) end++;
> +if ((f2 = getc(fp2)) == EOF) end++;
> +
> + if (end == 2) return 0;
> + if (end == 1) return 1;
> +if (f1 != f2) return 2;
> +}
> +}
> +
> +START_TEST(test_xml_pass)
> +
> +
> +
> + XML *xp;
> + xp = xml_create(2, "./test.xml");
> + ck_assert(xp != NULL);
> + xml_add_case(xp, 0,"test1");
> + xml_add_case(xp, 1,"test2");
> + xml_finish(xp);
> +
> +  FILE *fp, *fr;
> +  fr = fopen("./tests/data/reference.xml", "r");
> + ck_assert(fr != NULL);
> + fp = fopen("./test.xml", "r");
> + ck_assert(fp != NULL);
> +
> + ck_assert(filecmp(fr, fp) == 0);
> +
> + fclose(fr);
> + fclose(fp);
> + unlink("./test.xml");

Removed blanks and change to tabs instead of spaces.

> +
> +END_TEST
> +
> +START_TEST(test_xml_fail)
> + ck_assert(xml_create(2, "./") == NULL);
> +
> +END_TEST
> +
>  Suite *
>  utils_suite()
>  {
> @@ -252,6 +296,8 @@ utils_suite()
>

[yocto] [[PATCH][ptest-runner]] utils.c: Improve user notice of TIMEOUT

[Aníbal Limón]

Print exit status before TIMEOUT to give clear information
to the user about exit status before TIMEOUT and END.

[YOCTO #10842]

Signed-off-by: Aníbal Limón 
---
 utils.c | 14 ++
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/utils.c b/utils.c
index 77427e0..e5677ec 100644
--- a/utils.c
+++ b/utils.c
@@ -260,6 +260,7 @@ wait_child(const char *ptest_dir, const char *run_ptest, 
pid_t pid,
time_t sentinel;
int r;
 
+   int timeouted = 0;
int status;
int waitflags;
 
@@ -289,7 +290,7 @@ wait_child(const char *ptest_dir, const char *run_ptest, 
pid_t pid,
 
sentinel = time(NULL);
} else if (timeout >= 0 && ((time(NULL) - sentinel) > timeout)) 
{
-   fprintf(fps[0], "TIMEOUT: %s\n", ptest_dir);
+   timeouted = 1;
kill(pid, SIGKILL);
waitflags = 0;
}
@@ -298,6 +299,12 @@ wait_child(const char *ptest_dir, const char *run_ptest, 
pid_t pid,
break;
}
 
+   if (status) {
+   fprintf(fps[0], "\nERROR: Exit status is %d\n", status);
+   if (timeouted)
+   fprintf(fps[0], "TIMEOUT: %s\n", ptest_dir);
+   }
+
return status;
 }
 
@@ -351,10 +358,9 @@ run_ptests(struct ptest_list *head, int timeout, const 
char *progname,
 
status = wait_child(ptest_dir, p->run_ptest, 
child,
timeout, fds, fps);
-   if (status) {
-   fprintf(fp, "ERROR: Exit status is 
%d\n", status);
+   if (status)
rc += 1;
-   }
+
fprintf(fp, "END: %s\n", ptest_dir);
fprintf(fp, "%s\n", get_stime(stime, 
GET_STIME_BUF_SIZE));
}
-- 
2.1.4

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

[yocto] [meta-raspberrypi][PATCH v2 2/3] pitft: Include a pitft35r MACHINE_FEATURE

[Rob Woolley]

This MACHINE_FEATURE will automatically add the recommended
Adafruit configuration line to the Raspberry Pi config.txt.

Signed-off-by: Rob Woolley 
---
 recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index af55983..b3c5084 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -18,6 +18,7 @@ PR = "r5"
 PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
 PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
 PITFT28r="${@bb.utils.contains("MACHINE_FEATURES", "pitft28r", "1", "0", d)}"
+PITFT35r="${@bb.utils.contains("MACHINE_FEATURES", "pitft35r", "1", "0", d)}"
 
 VC4GRAPHICS="${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "1", "0", 
d)}"
 
@@ -99,6 +100,11 @@ do_deploy() {
 echo 
"dtoverlay=pitft28-resistive,rotate=90,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
 
+if [ "${PITFT35r}" = "1" ]; then
+echo "# Enable PITFT35r display" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtoverlay=pitft35-resistive,rotate=90,speed=4200,fps=20" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
+
 # UART support
 if [ "${ENABLE_UART}" = "1" ]; then
 echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
-- 
2.11.0

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

[yocto] [meta-raspberrypi][PATCH v2 3/3] pitft: Add documentation for pitft35r in README

[Rob Woolley]

The support for the PiTFT 3.5 inch resistive touchscreen is optional.
It may be enabled by adding the following line in local.conf:

MACHINE_FEATURES += "pitft pitft35r"

Signed-off-by: Rob Woolley 
---
 README | 1 +
 1 file changed, 1 insertion(+)

diff --git a/README b/README
index 9fdd5eb..e44475c 100644
--- a/README
+++ b/README
@@ -241,6 +241,7 @@ the modelname should be added as a MACHINE_FEATURES in 
local.conf like below:
 List of currently supported models:
 - pitft22
 - pitft28r
+- pitft35r
 
 3.O. Misc. display
 ==
-- 
2.11.0

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

[yocto] [meta-raspberrypi][PATCH v2 1/3] pitft: Include the pitft35r dtbo files

[Rob Woolley]

Include the pitft35r device tree blobs in the filesystem of the image.

Signed-off-by: Rob Woolley 
---
 conf/machine/include/rpi-base.inc | 1 +
 conf/machine/raspberrypi3-64.conf | 1 +
 2 files changed, 2 insertions(+)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index 092cbeb..9bcb91d 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -31,6 +31,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/lirc-rpi.dtbo \
 overlays/pitft22.dtbo \
 overlays/pitft28-resistive.dtbo \
+overlays/pitft35-resistive.dtbo \
 overlays/pps-gpio.dtbo \
 overlays/rpi-ft5406.dtbo \
 overlays/w1-gpio.dtbo \
diff --git a/conf/machine/raspberrypi3-64.conf 
b/conf/machine/raspberrypi3-64.conf
index ca10ed9..0efe3ff 100644
--- a/conf/machine/raspberrypi3-64.conf
+++ b/conf/machine/raspberrypi3-64.conf
@@ -23,6 +23,7 @@ KERNEL_DEVICETREE = " \
 overlays/lirc-rpi.dtbo \
 overlays/pitft22.dtbo \
 overlays/pitft28-resistive.dtbo \
+overlays/pitft35-resistive.dtbo \
 overlays/pps-gpio.dtbo \
 overlays/rpi-ft5406.dtbo \
 overlays/w1-gpio.dtbo \
-- 
2.11.0

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

[yocto] [meta-raspberrypi][PATCH v2 0/3] pitft: Add support for pitft35r

[Rob Woolley]

As requested, I have split the patch into separate commits for:

  1. dtbo inclusion
  2. rpi-config changes
  3. Documentation commit

I ordered them this way in case a user ever walked through the
commits in the git tree.  This way the prerequisites are present
before the feature is advertised in the documentation.

Hope this works for you.  Let me know if there are any additional 
changes that need to be made.

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

[yocto] Ad git revision to image name

[Grueninger, Tobias]

Hi,
I have a question:
I would like to automatically add the git Revison checksum to the generated 
Yocto image name, e.g. 'core-image-git_bc123456.img'
I fail miserably to add this in my image recipe - any help appreciated
Regards
Tobias

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

[yocto] [patchwork][PATCH v4] parsemail.py: Improve find_series_for_mail

[Jose Lamego]

Patch Series that are sent as replies to other Series with
different patch quantity are not appropriately detected as
such, breaking the thread and causing missing revisions.

This change improves the find_series_for_mail function to
appropriately detect when a message is part of a thread
by performing an additional patch-query and detecting cover
letters that are replies to cover letters.

[YOCTO #10959]

Signed-off-by: Jose Lamego 
---

Notes:
Changes in version 4: Only consider messages with Subject starting with "[" 
as possible cover letters, filtering out reply messages

 patchwork/bin/parsemail.py | 20 +---
 1 file changed, 17 insertions(+), 3 deletions(-)

diff --git a/patchwork/bin/parsemail.py b/patchwork/bin/parsemail.py
index 61c18b2..a68baa2 100755
--- a/patchwork/bin/parsemail.py
+++ b/patchwork/bin/parsemail.py
@@ -399,9 +399,9 @@ def find_content(project, mail):
 (x, n) = parse_series_marker(prefixes)
 refs = build_references_list(mail)
 is_root = refs == []
-is_cover_letter = is_root and x == 0
 patch_prefix = re.match('(\s*\[[^]]*\]\s*)*\[\s*PATCH',
 mail.get('Subject'))
+is_cover_letter = x == 0 and patch_prefix
 is_patch = patchbuf is not None and patch_prefix
 
 drop_patch = not is_attachment and \
@@ -441,7 +441,7 @@ def find_content(project, mail):
 
 (ret.series, ret.revision, ret.patch_order, n) = \
 find_series_for_mail(project, series_name, msgid, is_patch,
- ret.patch_order, n, refs)
+ ret.patch_order, n, refs, is_cover_letter)
 ret.revision.n_patches = n or 1
 
 date = mail_date(mail)
@@ -535,7 +535,7 @@ def find_patch_order(revisions, previous_patch, order, 
n_patches):
 #   - we need to create new revisions when the mail is actually a new version
 # of a previous patch
 def find_series_for_mail(project, name, msgid, is_patch, order, n_patches,
- refs):
+ refs, is_cover_letter):
 if refs == []:
 root_msgid = msgid
 else:
@@ -560,6 +560,20 @@ def find_series_for_mail(project, name, msgid, is_patch, 
order, n_patches,
 revision = revision.duplicate(exclude_patches=(order,))
 # series has been updated, grab the new instance
 series = revision.series
+else:
+try:
+prev_patch = SeriesRevisionPatch.objects.get(
+revision=revision, order=order).patch
+if prev_patch and not prev_patch.msgid == msgid:
+# this is a new patch in the thread
+revision = revision.duplicate(exclude_patches=(order,))
+series = revision.series
+except SeriesRevisionPatch.DoesNotExist:
+pass
+elif is_cover_letter and not refs == []:
+revision = revision.duplicate(
+exclude_patches=range(1, revision.n_patches+1),)
+series = revision.series
 except IndexError:
 if not name:
 name = SERIES_DEFAULT_NAME
-- 
2.7.4

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

Re: [yocto] Local repo no network help request

[Fabien Lahoudere]

On Wed, 2017-04-05 at 19:57 -0700, Matthew Phillips wrote:
> Hi all,
> 
> I am trying to do the following:
> 
> I have a local git repo, pulled manually from a remote repo (via a script).
> I have a .bb file set up referencing this repo. This .bb file includes
> (among other things):
> 
> > > SRC_URI = "git://${TOPDIR}/../sources/my-repo;protocol=file;branch=master"
> > > SRCREV = "${AUTOREV}"
> 
> I do not want to use the network (so BB_NO_NETWORK is 1).
> 
> Although the SRC_URI is pointing to the correct path, the yocto build
> fails because it tries to access the network.
> 
> How should I be doing this instead?

Can you use network features with ssh on localhost ?
Why don't you create tarball for delivery and cross compile for development?

> 
> I can run a script (preferably bash atm) before the build if doing
> something pre-build will help simplify anything.
> 
> Thank you,
> M
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Local repo no network help request

[Leonardo Sandoval]

On Wed, 2017-04-05 at 19:57 -0700, Matthew Phillips wrote:
> Hi all,
> 
> I am trying to do the following:
> 
> I have a local git repo, pulled manually from a remote repo (via a script).
> I have a .bb file set up referencing this repo. This .bb file includes
> (among other things):
> 
> >> SRC_URI = "git://${TOPDIR}/../sources/my-repo;protocol=file;branch=master"
> >> SRCREV = "${AUTOREV}"
> 

did you get the same result if you hard-coded the pathname? 




> I do not want to use the network (so BB_NO_NETWORK is 1).
> 
> Although the SRC_URI is pointing to the correct path, the yocto build
> fails because it tries to access the network.
> 
> How should I be doing this instead?
> 
> I can run a script (preferably bash atm) before the build if doing
> something pre-build will help simplify anything.
> 
> Thank you,
> M


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

Re: [yocto] Returning non-zero exit code

[Fabien Lahoudere]

On Wed, 2017-04-05 at 15:05 +, Natalia Theologou wrote:
> Hello, 
> 
> While I am trying to bitbake fsl-image-x11 I am having this error:
> 
> ERROR: Task 1570 
> (virtual:native:~/sources/poky/meta/recipes-support/gmp/gmp_5.1.1.bb, 
> do_compile)
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 78 tasks of which 74 didn't need to be rerun 
> and 2 failed.
> Waiting for 0 running tasks to finish:
> 
> Summary: 2 tasks failed:
>   virtual:native:~/sources/poky/meta/recipes-core/ncurses/ncurses_5.9.bb, 
> do_compile
>   virtual:native:~/sources/poky/meta/recipes-support/gmp/gmp_5.1.1.bb, 
> do_compile
> 
> Does anyone know how to solve it?

Can you give logs of do_compile for both recipe?

> 
> Thank you in advance, 
> Natalia Theologou
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Returning non-zero exit code

[Natalia Theologou]

Hello,

While I am trying to bitbake fsl-image-x11 I am having this error:

ERROR: Task 1570 
(virtual:native:~/sources/poky/meta/recipes-support/gmp/gmp_5.1.1.bb, 
do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 78 tasks of which 74 didn't need to be rerun and 
2 failed.
Waiting for 0 running tasks to finish:

Summary: 2 tasks failed:
  virtual:native:~/sources/poky/meta/recipes-core/ncurses/ncurses_5.9.bb, 
do_compile
  virtual:native:~/sources/poky/meta/recipes-support/gmp/gmp_5.1.1.bb, 
do_compile

Does anyone know how to solve it?

Thank you in advance,
Natalia Theologou
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] unable to create softlink for precompilied libraries

[Khem Raj]

On Thu, Apr 6, 2017 at 2:16 AM, chandrasekhar c
 wrote:
> Hi,
> I have added this FILES_${PN} += " ${libdir}/libMSOComm.so " line in my
> recipe still the issue is present
>

that may not be enough. .so are treated as symlinks and shoved into
-dev packages by default. if you need unversioned libraries then you
have to let the system know that its not a dev library symlink

FILES_${PN} += "${libdir}/*.so"
FILES_SOLIBSDEV = ""
INSANE_SKIP_${PN} += "dev-so"

> Thanks
> Chandra
>
> From: chandrasekhar c 
> Sent: Thu, 6 Apr 2017 14:39:04 GMT+0530
> To: "Fabien Lahoudere " 
> Cc: "yocto@yoctoproject.org" 
>
> Subject: Re: [yocto] unable to create softlink for precompilied libraries
>
> Hi ,
> No, I will do the changes and let you know the result.
>
> Regards,
> Chandrasekhar
>
> From: Fabien Lahoudere 
> Sent: Thu, 6 Apr 2017 14:10:30 GMT+0530
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] unable to create softlink for precompilied libraries
>
> On Thu, 2017-04-06 at 08:08 +, chandrasekhar c wrote:
>> Hi,
>> I have a third party precompilied libraries. I erota a recipe to copy to
>> rootfs and create   soft
>> links for the same. After doing bitbake it didnt throw any errors, but
>> when I check th rootfs it
>> didn't create any link file.
>> Below is my recipe
>>
>> do_install_append() {
>>   install -d ${D}${libdir}/
>> install -m 0777 ${S}/libMSO.so.1.2
>> ${D}${libdir}/libMSO.so.1.2
>> ln -sf libMSO.so.1.2 ${D}${libdir}/libMSO.so
>> install -m 0777 ${S}/libMSOComm.so.1.2
>> ${D}${libdir}/libMSOComm.so.1.2 //This is success
>> ln -sf libMSOComm.so.1.2 ${D}${libdir}/libMSOComm.so.1
>> //This is success
>> ln -sf libMSOComm.so.1  ${D}${libdir}/libMSOComm.so //This
>> is not happening
>> }
>> Can any one tell me a solution for this.
>
> Did you ship it with FILES_${PN} += " ${libdir}/libMSOComm.so " ?
>
>
>>
>> Thanks and Regards,
>> Chandrasekhar
> --
> ___
> 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 mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Install rootfs.tar.bz2 to ${D}/home/root/

[Enrico Joerns]

On 04/06/2017 10:37 AM, Josef Holzmayr wrote:

On 06.04.2017 10:31, Maier, Chris wrote:

Hi,

I want to create a deployable SD card image. My board (beaglebone
based) boots from SD card and runs a script which copies the
rootfs.tar.bz2 to the flash memory.
So how can I deploy a copy of the whole rootfs to ${D}/home/root?
A rootfs in the rootfs, does that make sense?

Any help is appreciated.

Chris
*i.A. **Chris Maier *
*Software-Entwicklungsingenieur *

Phone: +49 7152 203 6741 | Fax: +49 7152 203 76741 | c.ma...@geze.com
GEZE GmbH, Reinhold-Vöster-Straße 21-29, 71229 Leonberg | www.geze.com

SAVE PAPER - THINK BEFORE YOU PRINT


SAVE MAILS - THINK BEFORE YOU SEND


YouTube  Facebook
 LinkedIn
 Twitter
 Xing
 Geschäftsführung:
Brigitte Vöster-Alber (Vorsitzende), Andrea Alexandra Alber, Marc
Alber, Florian Birkenmayer
Vorsitzender des Aufsichtsrates: Prof. Dr. Dr. Ulli Arnold,
Amtsgericht Stuttgart HRB 250329, Tel: +49 7152 203 0
GEZE GmbH, Reinhold-Vöster-Straße 21-29, 71229 Leonberg, Germany



Why are you asking the exact same question the third time now?


Maybe your IT allows only outgoing mail transport?.. haha

Or its a misconfiguration of some sort of nodupes settings and you 
assume you have not sent it, yet?.. Just look at the answers, you have!



Enrico

--
Pengutronix e.K.   | Enrico Jörns|
Industrial Linux Solutions | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |

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

Re: [yocto] [OE-core] [PATCH 1/2] logrotate: Bump to 3.11.0

[Romain Perier]

Hello,


Le 06/04/2017 à 13:38, Richard Purdie a écrit :
> On Wed, 2017-04-05 at 17:05 +0200, Romain Perier wrote:
>> This commit updates the recipe to the last upstream tag. Then, as the
>> tarball no longer contains the pre-generated Makefile, inherit from
>> autotools
>>
>> [...]
>> -PACKAGECONFIG ?= "${@bb.utils.filter('DISTRO_FEATURES', 'acl
>> selinux', d)}"
>> +PACKAGECONFIG ?= "\
>> +${@bb.utils.contains('DISTRO_FEATURES', 'acl', 'acl', '', d)} \
>> +${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 'selinux',
>> '', d)} \
>> +"

Correct, I probably did something wrong during rebase.

> I'm not sure the above should be there, it reverts someone else's
> change?
>
> I am a little nervous of taking this at this point in the release
> too...

What do you think if we backport the systemd service and the systemd
timer from upstream into 3.9.1 and then add support for systemd in the
recipe ? (In the original patches, I have written systemd services
myself) The code of logrotate would be unchanged.

Regards,
Romain


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

Re: [yocto] [OE-core] [PATCH 1/2] logrotate: Bump to 3.11.0

[Richard Purdie]

On Wed, 2017-04-05 at 17:05 +0200, Romain Perier wrote:
> This commit updates the recipe to the last upstream tag. Then, as the
> tarball no longer contains the pre-generated Makefile, inherit from
> autotools
> 
> [...]

> -PACKAGECONFIG ?= "${@bb.utils.filter('DISTRO_FEATURES', 'acl
> selinux', d)}"
> +PACKAGECONFIG ?= "\
> +${@bb.utils.contains('DISTRO_FEATURES', 'acl', 'acl', '', d)} \
> +${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 'selinux',
> '', d)} \
> +"

I'm not sure the above should be there, it reverts someone else's
change?

I am a little nervous of taking this at this point in the release
too...

Cheers,

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

Re: [yocto] Fwd: iMX6UL - QtQuick - QtQuick2DRenderer

[Fabien Lahoudere]

On Thu, 2017-04-06 at 10:35 +0200, Stefano Zuín wrote:
> 
> 
> 
>  Mensaje reenviado 
> Asunto:   [yocto] iMX6UL - QtQuick - QtQuick2DRenderer
> Fecha:Wed, 5 Apr 2017 13:29:13 +0200
> De:   Stefano Zuín 
> Para: yocto@yoctoproject.org
> 
> Hi all,
> 
> I'm trying to run a graphical Qt application based in QtQuick2 and QML 
> (example calqtr) in my iMX6UL (Variscite's Dart6UL). As this device 
> doesn't have GPU, I have to use QtQuick2DRenderer to substitute openGL. 
> I'm using Ubuntu 14.04 64bits and Krogoth 2.1.2
> 
> I have the enterprise license, followed the Qt's instructions 
> (http://doc.qt.io/QtQuick2DRenderer/qtquick2drenderer-installation-guide.html)
>  
> and use the qmake built with meta-toolchain-qt5. So QtQuick2DRenderer is 
> correctly installed.
> 
> Then, before run the app, I declared export 
> QMLSCENE_DEVICE=softwarecontext before running the application. 
> Unfortunately, I get the next message when try to run a demo example:
> 
> ./calqlatr --platform linuxfb
> QML debugging is enabled. Only use this in a safe environment.
> This plugin does not support createPlatformOpenGLContext!
> Failed to create OpenGL context for format QSurfaceFormat(version 2.0, 
> options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize 
> -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples 
> -1, swapBehavior 2, swapInterval 1, profile  0)
> Aborted (core dumped)

Did you try to look at the core dumped. maybe the backtrace can help.

> 
> I did the SDK using meta-toolchain-qt5 and the image with fsl-image-qt5. 
> When I run a console app or a graphical which uses QtQuick 1, it works 
> correctly.
> 
> This is my conf/local.conf file:
> 
> MACHINE ??= 'imx6ul-var-dart'
> DISTRO ?= 'fsl-imx-fb'
> PACKAGE_CLASSES ?= "package_rpm"
> EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
> USER_CLASSES ?= "buildstats image-mklibs"
> PATCHRESOLVE = "noop"
> BB_DISKMON_DIRS = "\
>  STOPTASKS,${TMPDIR},1G,100K \
>  STOPTASKS,${DL_DIR},1G,100K \
>  STOPTASKS,${SSTATE_DIR},1G,100K \
>  STOPTASKS,/tmp,100M,100K \
>  ABORT,${TMPDIR},100M,1K \
>  ABORT,${DL_DIR},100M,1K \
>  ABORT,${SSTATE_DIR},100M,1K \
>  ABORT,/tmp,10M,1K"
> PACKAGECONFIG_append_pn-qemu-native = " sdl"
> PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
> CONF_VERSION = "1"
> 
> DL_DIR ?= "${BSPDIR}/downloads/"
> ACCEPT_FSL_EULA = "1"
> 
> # Add Eclipse debug and Qt creator support to your images
> EXTRA_IMAGE_FEATURES = " \
>  debug-tweaks \
>  tools-debug \
>  eclipse-debug \
> "
> 
> IMAGE_INSTALL_append = " \
>  tcf-agent \
>  openssh-sftp-server \
> qtbase-fonts \
>  qtbase-plugins \
>  qtbase-tools \
>  qtbase-examples \
>  qtdeclarative \
>  qtdeclarative-plugins \
>  qtdeclarative-tools \
>  qtdeclarative-examples \
>  qtdeclarative-qmlplugins \
>  qtquickcontrols-qmlplugins \
> "
> 
> # Use systemd instead of SysV init
> DISTRO_FEATURES_append = " systemd"
> VIRTUAL-RUNTIME_init_manager = "systemd"
> DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
> VIRTUAL-RUNTIME_initscripts = ""
> IMX_DEFAULT_DISTRO_FEATURES_append = " systemd"
> 
> 
> I think, that problem could be in configuring -opengl es2 in qtbase 
> recipe. But when I set it manually I get errors doing bitbake 
> fsl-image-qt5
> 
> 
> 
> Este correo electrónico y sus documentos adjuntos contienen información 
> privilegiada, personal y
> estrictamente confidencial, y está prohibida la copia, reenvío o utilización 
> de la información.
> Si usted no es la persona destinataria del presente mensaje, no está 
> autorizada a leerlo,
> retenerlo o difundirlo.
> 
> This e-mail and its attachments are privileged, confidential and contain 
> private information, and
> any sending, using or copy of its information is prohibited.
> Any person other than its intended recipient is not authorised to read, 
> retain or distribute this
> information.
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] unable to create softlink for precompilied libraries

[Fabien Lahoudere]

Can you check that the file is installed in image folder and in package in the 
WORKDIR of your
recipe?

On Thu, 2017-04-06 at 09:16 +, chandrasekhar c wrote:
> Hi,
> I have added this FILES_${PN} += " ${libdir}/libMSOComm.so " line in my 
> recipe still the issue is
> present
> 
> Thanks 
> Chandra
> 
> From: chandrasekhar c 
> Sent: Thu, 6 Apr 2017 14:39:04 GMT+0530
> To: "Fabien Lahoudere " 
> Cc: "yocto@yoctoproject.org" 
> Subject: Re: [yocto] unable to create softlink for precompilied libraries
> 
> Hi ,
> No, I will do the changes and let you know the result.
> 
> Regards,
> Chandrasekhar
> 
> From: Fabien Lahoudere 
> Sent: Thu, 6 Apr 2017 14:10:30 GMT+0530
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] unable to create softlink for precompilied libraries
> 
> On Thu, 2017-04-06 at 08:08 +, chandrasekhar c wrote:
> > Hi,  
> > I have a third party precompilied libraries. I erota a recipe to copy to 
> > rootfs and create  
> soft
> > links for the same. After doing bitbake it didnt throw any errors, but when 
> > I check th rootfs it
> > didn't create any link file.
> > Below is my recipe
> >  
> > do_install_append() {
> >                   install -d ${D}${libdir}/
> >                 install -m 0777 ${S}/libMSO.so.1.2 
> > ${D}${libdir}/libMSO.so.1.2
> >                 ln -sf libMSO.so.1.2 ${D}${libdir}/libMSO.so
> >                 install -m 0777 ${S}/libMSOComm.so.1.2 
> > ${D}${libdir}/libMSOComm.so.1.2 //This is
> success
> >                 ln -sf libMSOComm.so.1.2 ${D}${libdir}/libMSOComm.so.1 
> > //This is success
> >                 ln -sf libMSOComm.so.1  ${D}${libdir}/libMSOComm.so //This 
> > is not happening
> > }
> > Can any one tell me a solution for this.
> 
> Did you ship it with FILES_${PN} += " ${libdir}/libMSOComm.so " ?
> 
> 
> >  
> > Thanks and Regards,
> > Chandrasekhar
> --
> ___
> 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 mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] unable to create softlink for precompilied libraries

[chandrasekhar c]

Hi,I have added this FILES_${PN} += " 
${libdir}/libMSOComm.so " line in my recipe still the issue is 
presentThanks ChandraFrom: chandrasekhar c 
Sent: Thu, 6 Apr 2017 14:39:04 GMT+0530To: 
"Fabien Lahoudere " Cc: 
"yocto@yoctoproject.org" Subject: Re: 
[yocto] unable to create softlink for precompilied librariesHi ,No, I will do 
the changes and let you know the result.Regards,ChandrasekharFrom: Fabien 
Lahoudere Sent: Thu, 6 Apr 2017 
14:10:30 GMT+0530To: yocto@yoctoproject.orgSubject: Re: [yocto] unable to 
create softlink for precompilied librariesOn Thu, 2017-04-06 at 08:08 +, 
chandrasekhar c wrote:> Hi,  > I have a third party precompilied 
libraries. I erota a recipe to copy to rootfs and create   soft> links 
for the same. After doing bitbake it didnt throw any errors
 , but when I check th rootfs it> didn't create any link file.> Below 
is my recipe>  > do_install_append() {>       
            install -d ${D}${libdir}/>   
              install -m 0777 
${S}/libMSO.so.1.2 ${D}${libdir}/libMSO.so.1.2>         
        ln -sf libMSO.so.1.2 ${D}${libdir}/libMSO.so> 
                install -m 0777 
${S}/libMSOComm.so.1.2 ${D}${libdir}/libMSOComm.so.1.2 //This is success> 
                ln -sf 
libMSOComm.so.1.2 ${D}${libdir}/libMSOComm.so.1 //This is success>   
              ln -sf libMSOComm.so.1 
 ${D}${libdir}/libMSOComm.so //This is not happening> }> Can any one 
tell me a solution for this.Did you ship it with FILES_${PN} += " 
${libdir}/libMSOComm.so
  " ?>  > Thanks and Regards,> 
Chandrasekhar--___yocto mailing 
listyocto@yoctoproject.orghttps://lists.yoctoproject.org/listinfo/yocto 
--___yocto mailing 
listyocto@yoctoproject.orghttps://lists.yoctoproject.org/listinfo/yocto-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] unable to create softlink for precompilied libraries

[chandrasekhar c]

Hi ,No, I will do the changes and let you know the 
result.Regards,ChandrasekharFrom: Fabien Lahoudere 
Sent: Thu, 6 Apr 2017 14:10:30 
GMT+0530To: yocto@yoctoproject.orgSubject: Re: [yocto] unable to create 
softlink for precompilied librariesOn Thu, 2017-04-06 at 08:08 +, 
chandrasekhar c wrote:> Hi,  > I have a third party precompilied 
libraries. I erota a recipe to copy to rootfs and create   soft> links 
for the same. After doing bitbake it didnt throw any errors, but when I check 
th rootfs it> didn't create any link file.> Below is my recipe> 
 > do_install_append() {>             
      install -d ${D}${libdir}/>         
        install -m 0777 ${S}/libMSO.so.1.2 
${D}${libdir}/libMSO.so.1.2>             
    ln -sf libMSO.so.1.2 ${D}${libdir}/libMSO.so>   
               install -m 0777 
${S}/libMSOComm.so.1.2 ${D}${libdir}/libMSOComm.so.1.2 //This is success> 
                ln -sf 
libMSOComm.so.1.2 ${D}${libdir}/libMSOComm.so.1 //This is success>   
              ln -sf libMSOComm.so.1 
 ${D}${libdir}/libMSOComm.so //This is not happening> }> Can any one 
tell me a solution for this.Did you ship it with FILES_${PN} += " 
${libdir}/libMSOComm.so " ?>  > Thanks and Regards,> 
Chandrasekhar--___yocto mailing 
listyocto@yoctoproject.orghttps://lists.yoctoproject.org/listinfo/yocto-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Install rootfs.tar.bz2 to ${D}/home/root/

[Josef Holzmayr]

On 06.04.2017 10:31, Maier, Chris wrote:

Hi,

I want to create a deployable SD card image. My board (beaglebone based) 
boots from SD card and runs a script which copies the rootfs.tar.bz2 to 
the flash memory.

So how can I deploy a copy of the whole rootfs to ${D}/home/root?
A rootfs in the rootfs, does that make sense?

Any help is appreciated.

Chris
*i.A. **Chris Maier *
*Software-Entwicklungsingenieur *

Phone: +49 7152 203 6741 | Fax: +49 7152 203 76741 | c.ma...@geze.com
GEZE GmbH, Reinhold-Vöster-Straße 21-29, 71229 Leonberg | www.geze.com

SAVE PAPER - THINK BEFORE YOU PRINT
YouTube  Facebook 
 LinkedIn 
 Twitter 
 Xing 
 	Geschäftsführung: Brigitte 
Vöster-Alber (Vorsitzende), Andrea Alexandra Alber, Marc Alber, Florian 
Birkenmayer
Vorsitzender des Aufsichtsrates: Prof. Dr. Dr. Ulli Arnold, Amtsgericht 
Stuttgart HRB 250329, Tel: +49 7152 203 0

GEZE GmbH, Reinhold-Vöster-Straße 21-29, 71229 Leonberg, Germany



Why are you asking the exact same question the third time now?

--
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

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

Re: [yocto] unable to create softlink for precompilied libraries

[Fabien Lahoudere]

On Thu, 2017-04-06 at 08:08 +, chandrasekhar c wrote:
> Hi, 
> I have a third party precompilied libraries. I erota a recipe to copy to 
> rootfs and create  soft
> links for the same. After doing bitbake it didnt throw any errors, but when I 
> check th rootfs it
> didn't create any link file.
> Below is my recipe
>  
> do_install_append() {
>  install -d ${D}${libdir}/
>      install -m 0777 ${S}/libMSO.so.1.2 ${D}${libdir}/libMSO.so.1.2
>      ln -sf libMSO.so.1.2 ${D}${libdir}/libMSO.so
>      install -m 0777 ${S}/libMSOComm.so.1.2 
> ${D}${libdir}/libMSOComm.so.1.2 //This is success
>      ln -sf libMSOComm.so.1.2 ${D}${libdir}/libMSOComm.so.1 //This is 
> success
>      ln -sf libMSOComm.so.1 ${D}${libdir}/libMSOComm.so //This is not 
> happening
> }
> Can any one tell me a solution for this.

Did you ship it with FILES_${PN} += " ${libdir}/libMSOComm.so " ?


>  
> Thanks and Regards,
> Chandrasekhar
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Fwd: iMX6UL - QtQuick - QtQuick2DRenderer

[Stefano Zuín]

 Mensaje reenviado 
Asunto: [yocto] iMX6UL - QtQuick - QtQuick2DRenderer
Fecha:  Wed, 5 Apr 2017 13:29:13 +0200
De: Stefano Zuín 
Para:   yocto@yoctoproject.org



Hi all,

I'm trying to run a graphical Qt application based in QtQuick2 and QML
(example calqtr) in my iMX6UL (Variscite's Dart6UL). As this device
doesn't have GPU, I have to use QtQuick2DRenderer to substitute openGL.
I'm using Ubuntu 14.04 64bits and Krogoth 2.1.2

I have the enterprise license, followed the Qt's instructions
(http://doc.qt.io/QtQuick2DRenderer/qtquick2drenderer-installation-guide.html)
and use the qmake built with meta-toolchain-qt5. So QtQuick2DRenderer is
correctly installed.

Then, before run the app, I declared export
QMLSCENE_DEVICE=softwarecontext before running the application.
Unfortunately, I get the next message when try to run a demo example:

./calqlatr --platform linuxfb
QML debugging is enabled. Only use this in a safe environment.
This plugin does not support createPlatformOpenGLContext!
Failed to create OpenGL context for format QSurfaceFormat(version 2.0,
options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize
-1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples
-1, swapBehavior 2, swapInterval 1, profile  0)
Aborted (core dumped)

I did the SDK using meta-toolchain-qt5 and the image with fsl-image-qt5.
When I run a console app or a graphical which uses QtQuick 1, it works
correctly.

This is my conf/local.conf file:

MACHINE ??= 'imx6ul-var-dart'
DISTRO ?= 'fsl-imx-fb'
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS = "\
 STOPTASKS,${TMPDIR},1G,100K \
 STOPTASKS,${DL_DIR},1G,100K \
 STOPTASKS,${SSTATE_DIR},1G,100K \
 STOPTASKS,/tmp,100M,100K \
 ABORT,${TMPDIR},100M,1K \
 ABORT,${DL_DIR},100M,1K \
 ABORT,${SSTATE_DIR},100M,1K \
 ABORT,/tmp,10M,1K"
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
CONF_VERSION = "1"

DL_DIR ?= "${BSPDIR}/downloads/"
ACCEPT_FSL_EULA = "1"

# Add Eclipse debug and Qt creator support to your images
EXTRA_IMAGE_FEATURES = " \
 debug-tweaks \
 tools-debug \
 eclipse-debug \
"

IMAGE_INSTALL_append = " \
 tcf-agent \
 openssh-sftp-server \
qtbase-fonts \
 qtbase-plugins \
 qtbase-tools \
 qtbase-examples \
 qtdeclarative \
 qtdeclarative-plugins \
 qtdeclarative-tools \
 qtdeclarative-examples \
 qtdeclarative-qmlplugins \
 qtquickcontrols-qmlplugins \
"

# Use systemd instead of SysV init
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""
IMX_DEFAULT_DISTRO_FEATURES_append = " systemd"


I think, that problem could be in configuring -opengl es2 in qtbase
recipe. But when I set it manually I get errors doing bitbake
fsl-image-qt5



Este correo electrónico y sus documentos adjuntos contienen información 
privilegiada, personal y estrictamente confidencial, y está prohibida la copia, 
reenvío o utilización de la información.
Si usted no es la persona destinataria del presente mensaje, no está autorizada 
a leerlo, retenerlo o difundirlo.

This e-mail and its attachments are privileged, confidential and contain 
private information, and any sending, using or copy of its information is 
prohibited.
Any person other than its intended recipient is not authorised to read, retain 
or distribute this information.


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


Este correo electrónico y sus documentos adjuntos contienen información 
privilegiada, personal y estrictamente confidencial, y está prohibida la copia, 
reenvío o utilización de la información.
Si usted no es la persona destinataria del presente mensaje, no está autorizada 
a leerlo, retenerlo o difundirlo.

This e-mail and its attachments are privileged, confidential and contain 
private information, and any sending, using or copy of its information is 
prohibited.
Any person other than its intended recipient is not authorised to read, retain 
or distribute this information.

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

[yocto] Install rootfs.tar.bz2 to ${D}/home/root/

[Maier, Chris]

Hi, 

I want to create a deployable SD card image. My board (beaglebone based) boots 
from SD card and runs a script which copies the rootfs.tar.bz2 to the flash 
memory. 
So how can I deploy a copy of the whole rootfs to ${D}/home/root? 
A rootfs in the rootfs, does that make sense? 

Any help is appreciated. 

Chris

 i.A. Chris Maier 
Software-Entwicklungsingenieur 

Phone: +49 7152 203 6741 | Fax: +49 7152 203 76741 | c.ma...@geze.com 
GEZE GmbH, Reinhold-Vöster-Straße 21-29, 71229 Leonberg | www.geze.com 
SAVE PAPER - THINK BEFORE YOU PRINT
   Geschäftsführung: Brigitte Vöster-Alber (Vorsitzende), Andrea 
Alexandra Alber, Marc Alber, Florian Birkenmayer 
Vorsitzender des Aufsichtsrates: Prof. Dr. Dr. Ulli Arnold, Amtsgericht 
Stuttgart HRB 250329, Tel: +49 7152 203 0 
GEZE GmbH, Reinhold-Vöster-Straße 21-29, 71229 Leonberg, Germany 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] unable to create softlink for precompilied libraries

[chandrasekhar c]

Hi, I have a third party precompilied libraries. I erota a recipe to copy 
to rootfs and create  soft links for the same. After doing bitbake it 
didnt throw any errors, but when I check th rootfs it didn't create any 
link file.Below is my recipe do_install_append() 
{ install -d 
${D}${libdir}/     install -m 0777 
${S}/libMSO.so.1.2 ${D}${libdir}/libMSO.so.1.2   
  ln -sf libMSO.so.1.2 
${D}${libdir}/libMSO.so     install -m 
0777 ${S}/libMSOComm.so.1.2 ${D}${libdir}/libMSOComm.so.1.2 //This is 
success     ln -sf libMSOComm.so.1.2 
${D}${libdir}/libMSOComm.so.1 //This is success   
  ln -sf 
libMSOComm.so.1 ${D}${libdir}/libMSOComm.so //This is not happening}
Can any one tell me a solution for this. 
Thanks and Regards,Chandrasekhar-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Install rootfs.tar.bz2 to ${D}/home/root/

[Enrico Joerns]

Hi Chris,

On 04/06/2017 08:50 AM, Josef Holzmayr wrote:

Hi,

On 06.04.2017 08:41, Maier, Chris wrote:

Hi,

I want to create a deployable SD card image. My board (beaglebone
based) boots from SD card and runs a script which copies the
rootfs.tar.bz2 to the flash memory.

So how can I deploy a copy of the whole rootfs to ${D}/home/root?

A rootfs in the rootfs, does that make sense?


Partially. Sounds like you want to invent your own update mechanism.
Have you had a look at the already existing ones, specifically swupdate?


if you intend to build an update system, Josef is right, choose an 
existing (image/archive-based) one. Here is a good overview and 
comparison of update frameworks currently supported by meta layers:


  https://wiki.yoctoproject.org/wiki/System_Update

If you intend to do this for factory bootstrapping your device instead, 
i.e. you also set up the flash partitioning etc. this is partly out of 
the scope of these tools. A typical setup we use for this is a rootfs 
partition on your disk that you start your factory system from, and a 
second data partition where you place your rootfs in.


We use the `genimage` [1] tool for creating such images that also allows 
packing build images into a data partition, but this should be possible 
with Yocto's `wic` [2], too.


Note that you can also do a two-step approach where you set-up the flash 
storage with a script first and then already use an update tool to 
deploy the initial content (from the data partition) to it. Note that 
not all tools will support this by their configuration, currently.



Best regards, Enrico


[1] https://git.pengutronix.de/cgit/meta-ptx/tree/classes/genimage.bbclass
[2] 
http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#creating-partitioned-images


--
Pengutronix e.K.   | Enrico Jörns|
Industrial Linux Solutions | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |

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