Re: [yocto] unable to get checksum SRC_URI file could not be found

[Robert Yang]

On 07/10/2014 01:16 PM, jags gediya wrote:

I am building yocto for freescale imx6sl evolution kit. For checking
in source code on svn , i have deleted all .git and .gitignore from
the meta directories. Then i have checkout the source code, and tried
to build that. While building i am getting the warning

Unable to get checksum for rfkill SRC_URI entry
dont.call.git.rev-parse.on.parent.dir.patch: file could not be found

What can be the reason of it?


It can't find the dont.call.git.rev-parse.on.parent.dir.patch, there should
be a line like:

SRC_URI ="file://dont.call.git.rev-parse.on.parent.dir.patch"

Try to grep dont.call.git.rev-parse.on.parent.dir.patch in the meta layers.


Will it create any problem?


Yes, it would cause problems if you build the recipe.

// Robert



Thanks,
Jags


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

[yocto] unable to get checksum SRC_URI file could not be found

[jags gediya]

I am building yocto for freescale imx6sl evolution kit. For checking
in source code on svn , i have deleted all .git and .gitignore from
the meta directories. Then i have checkout the source code, and tried
to build that. While building i am getting the warning

Unable to get checksum for rfkill SRC_URI entry
dont.call.git.rev-parse.on.parent.dir.patch: file could not be found

What can be the reason of it?
Will it create any problem?

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

[yocto] [meta-security][PATCH] checksec: Add new alsr pic pie test script

[Armin Kuster]

Signed-off-by: Armin Kuster 
---
 recipes-security/checksec/checksec_1.5.bb   |  16 +
 recipes-security/checksec/files/checksec.sh | 882 
 2 files changed, 898 insertions(+)
 create mode 100644 recipes-security/checksec/checksec_1.5.bb
 create mode 100644 recipes-security/checksec/files/checksec.sh

diff --git a/recipes-security/checksec/checksec_1.5.bb 
b/recipes-security/checksec/checksec_1.5.bb
new file mode 100644
index 000..49ecc28
--- /dev/null
+++ b/recipes-security/checksec/checksec_1.5.bb
@@ -0,0 +1,16 @@
+SUMMARY = "Program radominization"
+DESCRIPTION = "The checksec.sh script is designed to test what standard Linux 
OS and PaX security features are being used."
+SECTION = "security"
+LICENSE = "BSD"
+HOMEPAGE="http://www.trapkit.de/tools/checksec.html";
+
+LIC_FILES_CHKSUM = "file://checksec.sh;md5=075996be339ab16ad7b94d6de3ee07bd"
+
+SRC_URI = "file://checksec.sh"
+
+S = "${WORKDIR}"
+
+do_install() {
+install -d ${D}${bindir}
+install -m 0755 ${WORKDIR}/checksec.sh${D}${bindir}
+}
diff --git a/recipes-security/checksec/files/checksec.sh 
b/recipes-security/checksec/files/checksec.sh
new file mode 100644
index 000..dd1f72e
--- /dev/null
+++ b/recipes-security/checksec/files/checksec.sh
@@ -0,0 +1,882 @@
+#!/bin/bash
+#
+# The BSD License (http://www.opensource.org/licenses/bsd-license.php) 
+# specifies the terms and conditions of use for checksec.sh:
+#
+# Copyright (c) 2009-2011, Tobias Klein.
+# All rights reserved.
+#
+# Redistribution and use in source and binary forms, with or without 
+# modification, are permitted provided that the following conditions 
+# are met:
+# 
+# * Redistributions of source code must retain the above copyright 
+#   notice, this list of conditions and the following disclaimer.
+# * Redistributions in binary form must reproduce the above copyright 
+#   notice, this list of conditions and the following disclaimer in 
+#   the documentation and/or other materials provided with the 
+#   distribution.
+# * Neither the name of Tobias Klein nor the name of trapkit.de may be 
+#   used to endorse or promote products derived from this software 
+#   without specific prior written permission.
+#
+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 
+# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 
+# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS 
+# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE 
+# COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 
+# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 
+# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS 
+# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED 
+# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, 
+# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF 
+# THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH 
+# DAMAGE.
+#
+# Name: checksec.sh
+# Version : 1.5
+# Author  : Tobias Klein
+# Date: November 2011
+# Download: http://www.trapkit.de/tools/checksec.html
+# Changes : http://www.trapkit.de/tools/checksec_changes.txt
+#
+# Description:
+#
+# Modern Linux distributions offer some mitigation techniques to make it 
+# harder to exploit software vulnerabilities reliably. Mitigations such 
+# as RELRO, NoExecute (NX), Stack Canaries, Address Space Layout 
+# Randomization (ASLR) and Position Independent Executables (PIE) have 
+# made reliably exploiting any vulnerabilities that do exist far more 
+# challenging. The checksec.sh script is designed to test what *standard* 
+# Linux OS and PaX (http://pax.grsecurity.net/) security features are being 
+# used.
+#
+# As of version 1.3 the script also lists the status of various Linux kernel 
+# protection mechanisms.
+#
+# Credits:
+#
+# Thanks to Brad Spengler (grsecurity.net) for the PaX support.
+# Thanks to Jon Oberheide (jon.oberheide.org) for the kernel support.
+# Thanks to Ollie Whitehouse (Research In Motion) for rpath/runpath support.
+# 
+# Others that contributed to checksec.sh (in no particular order):
+#
+# Simon Ruderich, Denis Scherbakov, Stefan Kuttler, Radoslaw Madej,
+# Anthony G. Basile, Martin Vaeth and Brian Davis. 
+#
+
+# global vars
+have_readelf=1
+verbose=false
+
+# FORTIFY_SOURCE vars
+FS_end=_chk
+FS_cnt_total=0
+FS_cnt_checked=0
+FS_cnt_unchecked=0
+FS_chk_func_libc=0
+FS_functions=0
+FS_libc=0
+ 
+# version information
+version() {
+  echo "checksec v1.5, Tobias Klein, www.trapkit.de, November 2011"
+  echo 
+}
+
+# help
+help() {
+  echo "Usage: checksec [OPTION]"
+  echo
+  echo "Options:"
+  echo
+  echo "  --file "
+  echo "  --dir  [-v]"
+  echo "  --proc "
+  echo "  --proc-all"
+  echo "  --proc-libs "
+  echo "  --kernel"
+  echo "  --fortify-file "
+  echo "  --fortify-proc "
+  echo "  --version"
+  echo "  --help"
+  echo
+  echo "For more information, see:"
+  

[yocto] [meta-security][PATCH] pinentry: Fix do_package_qa issue

[Armin Kuster]

This fixes;
ERROR: QA Issue: pinentry: The compile log indicates that host include and/or 
library paths were used.

Signed-off-by: Armin Kuster 
---
 recipes-security/pinentry/pinentry_0.8.3.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/recipes-security/pinentry/pinentry_0.8.3.bb 
b/recipes-security/pinentry/pinentry_0.8.3.bb
index 0043c23..3209e53 100644
--- a/recipes-security/pinentry/pinentry_0.8.3.bb
+++ b/recipes-security/pinentry/pinentry_0.8.3.bb
@@ -11,4 +11,5 @@ SRC_URI[sha256sum] = 
"568b0b09b50b2388a4f94d704d5bcb28718ecd4654ed1acc43ab1f97d9
 
 inherit autotools
 
-EXTRA_OECONF +="--disable-pinentry-gtk2 --disable-pinentry-qt 
--disable-pinentry-qt4 --without-x --enable-ncurses"
+EXTRA_OECONF +="--disable-pinentry-gtk2 --disable-pinentry-qt 
--disable-pinentry-qt4 --without-x --enable-ncurses \
+--with-ncurses-include-dir=${STAGING_INCDIR} "
-- 
1.9.1

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

[yocto] [meta-security][PATCH] nmap: update to 6.46

[Armin Kuster]

Updated to later version on nmap.
remove patch which is included in update
Added ndiff package
Include zenmap build changes but commented out for now and untested

Signed-off-by: Armin Kuster 
---
 recipes-security/nmap/files/lua.patch | 79 ---
 recipes-security/nmap/nmap_6.25.bb| 24 ---
 recipes-security/nmap/nmap_6.46.bb| 36 
 3 files changed, 36 insertions(+), 103 deletions(-)
 delete mode 100644 recipes-security/nmap/files/lua.patch
 delete mode 100644 recipes-security/nmap/nmap_6.25.bb
 create mode 100644 recipes-security/nmap/nmap_6.46.bb

diff --git a/recipes-security/nmap/files/lua.patch 
b/recipes-security/nmap/files/lua.patch
deleted file mode 100644
index 7cb86ab..000
--- a/recipes-security/nmap/files/lua.patch
+++ /dev/null
@@ -1,79 +0,0 @@
-Added missing definitions which caused failuire at do_configure
-with --without-liblua option.
-
-Upstream Status : pending
-
-Signed-off-by: Andrei Dinu 
 a/output.h
-+++ b/output.h
-@@ -226,6 +226,10 @@
- void printscriptresults(ScriptResults *scriptResults, stype scantype);
- 
- void printhostscriptresults(Target *currenths);
-+
-+/*This is a helper function to determine the ordering of the script results
-+  based on their id */
-+bool comparescriptids(ScriptResult first, ScriptResult second);
- #endif
- 
- /* Print a table with traceroute hops. */
-@@ -253,8 +257,4 @@
-were found. */
- void printdatafilepaths();
- 
--/*This is a helper function to determine the ordering of the script results
--  based on their id */
--bool comparescriptids(ScriptResult first, ScriptResult second);
--
- #endif /* OUTPUT_H */
 a/output.cc
-+++ b/output.cc
-@@ -2613,6 +2613,7 @@
-   }
- }
- 
-+#ifndef NOLUA
- /*This is a helper function to determine the ordering of the script results
-   based on their id */
- bool comparescriptids(ScriptResult first, ScriptResult second){
-@@ -2625,5 +2626,6 @@
- else
- return false;
- }
-+#endif
- 
- 
 a/portlist.cc
-+++ b/portlist.cc
-@@ -144,6 +144,7 @@
-   }
- }
- 
-+#ifndef NOLUA
- void Port::freeScriptResults(void)
- {
- while (!scriptResults.empty()) {
-@@ -151,6 +152,7 @@
- scriptResults.pop_front();
- }
- }
-+#endif
- 
- /* Fills in namebuf (as long as there is space in buflen) with the
-Name nmap normal output will use to describe the port.  This takes
 a/Target.cc
-+++ b/Target.cc
-@@ -162,10 +162,12 @@
- 
- Target::~Target() {
-   FreeInternal();
-+#ifndef NOLUA
-   while (!scriptResults.empty()) {
- scriptResults.front().clear();
- scriptResults.pop_front();
-   }
-+#endif
- }
- 
- void Target::FreeInternal() {
-
diff --git a/recipes-security/nmap/nmap_6.25.bb 
b/recipes-security/nmap/nmap_6.25.bb
deleted file mode 100644
index 5efcc70..000
--- a/recipes-security/nmap/nmap_6.25.bb
+++ /dev/null
@@ -1,24 +0,0 @@
-SUMMARY = "network auditing tool"
-DESCRIPTION = "Nmap ("Network Mapper") is a free and open source (license) 
utility for network discovery and security auditing."
-SECTION = "security"
-LICENSE = "GPL-2.0"
-LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
-FILES_${PN} += "${target_datadir}/ncat"
-
-SRC_URI = "http://nmap.org/dist/${PN}-${PV}.tar.bz2 \
-   file://lua.patch"
-
-SRC_URI[md5sum] = "fcc80f94ff3adcb11eedf91092ea6f5e"
-SRC_URI[sha256sum] = 
"3349cc6d36b86b95ca2b8075d16615a3a598cef494920d6652f9a8bf9f7660b5"
-
-inherit autotools-brokensep
-
-DEPENDS = "libpcap"
-
-EXTRA_OECONF = "--without-liblua --without-zenmap --without-subversion 
--with-pcap=linux"
-
-do_configure() {
-autoconf
-oe_runconf
-}
-
diff --git a/recipes-security/nmap/nmap_6.46.bb 
b/recipes-security/nmap/nmap_6.46.bb
new file mode 100644
index 000..42db71f
--- /dev/null
+++ b/recipes-security/nmap/nmap_6.46.bb
@@ -0,0 +1,36 @@
+SUMMARY = "network auditing tool"
+DESCRIPTION = "Nmap ("Network Mapper") is a free and open source (license) 
utility for network discovery and security auditing."
+SECTION = "security"
+LICENSE = "GPL-2.0"
+LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
+FILES_${PN} += "${target_datadir}/ncat"
+
+SRC_URI = "http://nmap.org/dist/${BPN}-${PV}.tar.bz2";
+
+SRC_URI[md5sum] = "5a36ad3a63d5b7ea5514f745a397436a"
+SRC_URI[sha256sum] = 
"3f89d9053c69507fe9533c40188a6561d49607a37b1db6380aed9039d4883137"
+
+inherit autotools-brokensep
+
+DEPENDS = "libpcap"
+
+EXTRA_OECONF = "--without-liblua --without-zenmap --without-subversion 
--with-pcap=linux"
+
+do_configure() {
+autoconf
+oe_runconf
+}
+
+# should add a conditional for "--without-zenmap" test. 
+# zenmap builds if the below are uncommented. Not tested
+#PACKAGES =+ "${PN}-zenmap"
+#FILES_${PN}-zenmap = "/usr/share/zenmap/*"
+
+#  should add a conditional based for "--without-ndiff"
+PACKAGES =+ "${PN}-python"
+DESCRIPTION_${PN}-python = \
+"The ${PN}-python package includes the ndiff utility. \
+Ndiff is a tool to ai

Re: [yocto] Environment Variables being unset by bitbake?

[Patrick Doyle]

Oh!  I think I know the answer to this one!

Check out BB_ENV_EXTRAWHITE at
http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#var-BB_ENV_EXTRAWHITE.
If you set that to something like JAVA_HOME, that might do what you
want.

--wpd


On Wed, Jul 9, 2014 at 4:58 PM, Allen Kennedy Jr.
 wrote:
> I am trying to run java program from a recipe.
>
> I get an error that JAVA_HOME is not set.
> I can verify that JAVA_HOME is set by echo $JAVA_HOME.
>
> I can then run the program without issue, but from within a recipe it
> seems that $JAVA_HOME is unset.
>
> I have verified this with 'bbnote "java is here: ${JAVA_HOME}"' from within
> a recipe.
>
> Any ideas why or how this is getting unset, and how to fix?
> I couldn't find any documentation that talks about this.
>
> Thanks
>
> --
> ___
> 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] Environment Variables being unset by bitbake?

[Allen Kennedy Jr.]

I am trying to run java program from a recipe.

I get an error that JAVA_HOME is not set.
I can verify that JAVA_HOME is set by echo $JAVA_HOME.

I can then run the program without issue, but from within a recipe it
seems that $JAVA_HOME is unset.

I have verified this with 'bbnote "java is here: ${JAVA_HOME}"' from within
a recipe.

Any ideas why or how this is getting unset, and how to fix?
I couldn't find any documentation that talks about this.

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

Re: [yocto] Inadvertent RootFS permission pollution

[Bollinger, Seth]

On 7/9/14, 11:46 AM, "Saul Wold"  wrote:

>On 07/09/2014 08:18 AM, Christopher Larson wrote:
>> On Wed, Jul 9, 2014 at 7:37 AM, Bollinger, Seth
>>
>> wrote:
>>
>>> I recently ran into a problem where I had trouble determining why the
>>> setgid bit was set in my rootfs.  It turns out that debian has this
>>>bit set
>>> on /usr/local (where I was building from), and thus inherited this bit
>>>from
>>> that directory tree.  This surprised me, so I thought I would pass it
>>>along
>>> in case it saves anyone else some time.
>>
>>
>> Ah, yes, I've hit this in the past too, thanks for bringing it up, we'll
>> have to resolve that -- perhaps have bitbake chmod g-s ${TMPDIR} when
>>it's
>> created?
>>
>>
>>
>If you have not already filed a bug for this can some one please do that
>so it does not get lost or forgotten.

Sure thing, I can do it.

Seth

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

Re: [yocto] Inadvertent RootFS permission pollution

[Saul Wold]

On 07/09/2014 08:18 AM, Christopher Larson wrote:

On Wed, Jul 9, 2014 at 7:37 AM, Bollinger, Seth 
wrote:


I recently ran into a problem where I had trouble determining why the
setgid bit was set in my rootfs.  It turns out that debian has this bit set
on /usr/local (where I was building from), and thus inherited this bit from
that directory tree.  This surprised me, so I thought I would pass it along
in case it saves anyone else some time.



Ah, yes, I've hit this in the past too, thanks for bringing it up, we'll
have to resolve that -- perhaps have bitbake chmod g-s ${TMPDIR} when it's
created?



If you have not already filed a bug for this can some one please do that 
so it does not get lost or forgotten.


Thanks
Sau!

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

[yocto] Oracle Java for ARM?

[Joe Nicholson]

 

Hi Guys 

What's the best way of bringing in Oracle's Java JRE for ARM? 

The meta-oracle-java layer looks Intel only at the moment :-( 

Cheers! 

Joe 

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

Re: [yocto] Installing a directory tree of files into the target filesystem

[Joe Nicholson]

 

Thanks Adam. 

I don't have any major permissions issues either, so will definitely try
that. I assume I could just explicitly set the permissions on the target
directory as a later step in do_install if needed. 

Thanks also for the link. 

Cheers! 

Joe 

On 2014-07-09 14:56, Adam Hughes wrote: 

> Hi Joe,
> 
>> First post on here :-)
> 
> My first post too.
> 
>> I'd like to create a recipe that copies a whole directory tree of files into 
>> a directory on the output filesystem.
> 
> I faced the same problem, and resorted to "cp -r" (after making sure the 
> directory was there using "install -d"). In my case, I didn't need to mess 
> with permissions so I didn't need to full power of install.
> 
> See http://superuser.com/questions/229883/how-is-install-c-different-from-cp 
> [1] for a bit more chapter and verse.
> 
> Cheers,
> 
> Adam

 

Links:
--
[1]
http://superuser.com/questions/229883/how-is-install-c-different-from-cp
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Inadvertent RootFS permission pollution

[Christopher Larson]

On Wed, Jul 9, 2014 at 7:37 AM, Bollinger, Seth 
wrote:

> I recently ran into a problem where I had trouble determining why the
> setgid bit was set in my rootfs.  It turns out that debian has this bit set
> on /usr/local (where I was building from), and thus inherited this bit from
> that directory tree.  This surprised me, so I thought I would pass it along
> in case it saves anyone else some time.


Ah, yes, I've hit this in the past too, thanks for bringing it up, we'll
have to resolve that -- perhaps have bitbake chmod g-s ${TMPDIR} when it's
created?
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Inadvertent RootFS permission pollution

[Bollinger, Seth]

Hello,

I recently ran into a problem where I had trouble determining why the setgid 
bit was set in my rootfs.  It turns out that debian has this bit set on 
/usr/local (where I was building from), and thus inherited this bit from that 
directory tree.  This surprised me, so I thought I would pass it along in case 
it saves anyone else some time.

Thanks,

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

Re: [yocto] File system for alternate partition

[Bollinger, Seth]

>I'm not sure without digging into it further (which I'm unable to do at
>the 
>moment, perhaps someone else can.)

Just as an FYI for anyone who might find this thread interesting, I fixed
the problem by adding another hook into poky/lib/oe/image.py before the
IMAGE_CMD hook.

It defaults to doing nothing, but can be overridden by image recipes to
remove directories that have no value for the particular image.

diff --git a/meta/lib/oe/image.py b/meta/lib/oe/image.py
index c9b9033..c74821f 100644
--- a/meta/lib/oe/image.py
+++ b/meta/lib/oe/image.py
@@ -274,6 +274,7 @@ class Image(ImageDepGraph):
 bb.data.update_data(localdata)
 localdata.setVar('type', type)
 
+cmds.append("\t" + (localdata.getVar("IMAGE_CLEAN_FS",
True) or ""))
 cmds.append("\t" + localdata.getVar("IMAGE_CMD", True))
 cmds.append(localdata.expand("\tcd ${DEPLOY_DIR_IMAGE}"))


Seth

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

Re: [yocto] Installing a directory tree of files into the target filesystem

[Adam Hughes]

Hi Joe,
> First post on here :-)

My first post too.

> I'd like to create a recipe that copies a whole directory tree
> of files into a directory on the output filesystem.

I faced the same problem, and resorted to "cp -r" (after making sure the 
directory was there using "install -d").  In my case, I didn't need to mess 
with permissions so I didn't need to full power of install.

See http://superuser.com/questions/229883/how-is-install-c-different-from-cp 
for a bit more chapter and verse.

Cheers,

Adam

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

Re: [yocto] Aarch64 support

[Maxin B. John]

Hi Atul,

On Wed, Jul 09, 2014 at 06:16:31PM +0530, atulkumar singh wrote:
> Hi Maxin,
> 
> I have added three folder “meta-aarch64”, “meta-linaro” and
> “meta-linaro-toolchain” under my poky directory.
> I also have updated my bblayer.conf with:-
> BBLAYERS ?= " \
>   /home/atulk/yocto/poky-master/meta \
> /home/atulk/yocto/poky-master/meta-yocto \
>   /home/atulk/yocto/poky-master/meta-yocto-bsp \
>   /home/atulk/yocto/poky-master/meta-aarch64 \
> /home/atulk/yocto/poky-master/meta-linaro \
>   /home/atulk/yocto/poky-master/meta-linaro-toolchain \
>   "
> And local.conf MACHINE ??= "genericarmv8"
> But while building bitbake with meta-toolchain for aarch64 support, I am
> getting error as “ERROR: Layer 'linaro' depends on layer 'networking-layer',
> but this layer is not enabled in your configuration”.
This means, you need meta-openembedded to build it. Add these in your 
bblayer.conf:

meta-openembedded/meta-networking
meta-openembedded/meta-oe

> Do you have any comments about building the same.
> Also please note that I don’t need any external toolchain support as I wish to
> build my own toolchain.
> 
> Thanks and Regards,
> ATUL KUMAR SINGH
Best Regards,
Maxin
> 
> On 8 Jul 2014 19:52, "Maxin B. John"  wrote:
 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Understanding "Package groups"

[Stefan Hofmann]

Hi Rudolf,

thank you for your explanation. bash has not been installed, but HOB did some 
changes on the configuration files and I modified the distribution. I deleted 
everything and created my own image receipe. It works fine now.

Regards,
Stefan

Am 01.07.2014 um 22:34 schrieb Rudolf Streif :

> Hi Stefan,
> 
> You probably have found the explanation on package groups in the reference 
> manual [1].
> 
> Package groups are recipes with the sole purpose to create dependencies to 
> simplify image creation. A package group recipe bundles multiple packages 
> together and then instead of having to explicitly specify each package in the 
> IMAGE_INSTALL variable you can simply specify the package group name.
> 
> Package group recipes look like this (from the manual):
> 
> DESCRIPTION = "My Custom Package Groups"
> 
>  inherit packagegroup
> 
>  PACKAGES = "\
>  packagegroup-custom-apps \
>  packagegroup-custom-tools \
>  "
> 
>  RDEPENDS_packagegroup-custom-apps = "\
>  dropbear \
>  portmap \
>  psplash"
> 
>  RDEPENDS_packagegroup-custom-tools = "\
>  oprofile \
>  oprofileui-server \
>  lttng-control \
>  lttng-viewer"
> 
>  RRECOMMENDS_packagegroup-custom-tools = "\
>  kernel-module-oprofile"
> 
> 
> Like any recipe they have a description. They inherit the 
> packagegroup.bbclass. A package group recipe can define multiple package 
> groups in the PACKAGES variable. For each package group listed in PACKAGES 
> you will then need to specify the packages that actually go into them with 
> conditional RDEPENDS_ variables.
> 
> Package groups are only relevant for the YP build system. They do not create 
> package grouping for the package manager that you are using for your target. 
> However, if you select a package group from HOB then all of the packages 
> specified in that group should be installed in your target's rootfs by YP.
> 
> Rudi
> 
> 
> 
> [1] 
> http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#usingpoky-extend-customimage-customtasks
> 
> 
> On Tue, Jul 1, 2014 at 10:05 AM, Stefan Hofmann  
> wrote:
> Hi,
> 
> I made my first steps with yocto and everything worked fine so far. But now I 
> am struggling with "package groups". What I basically want, is a image for a 
> base system, which allows me to install additional packages over the air with 
> opkg. In my imagination package groups are something like preselected 
> packages, which need to be installed at once similar like it is handled in 
> Debian for X11-support for example. Is this right ? I have built 
> core-image-base for testing purposes and tried to figure out the dependencies 
> by using the Hob tool. It says that bash will be installed and the group 
> "base/shell" is responsible for that. However it is not installed, only ash 
> and I cannot find a package group "package-group-base-shell" in the receipes. 
> It does however exist in the work directory. So now I am somewhat confused.
> 
> Regards,
> Stefan
> 
> -- 
> 
> 
> 
> --
> ___
> 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] Aarch64 support

[atulkumar singh]

Hi Maxin,

I have added three folder “meta-aarch64”, “meta-linaro” and
“meta-linaro-toolchain” under my poky directory.
I also have updated my bblayer.conf with:-
BBLAYERS ?= " \
  /home/atulk/yocto/poky-master/meta \
/home/atulk/yocto/poky-master/meta-yocto \
  /home/atulk/yocto/poky-master/meta-yocto-bsp \
  /home/atulk/yocto/poky-master/meta-aarch64 \
/home/atulk/yocto/poky-master/meta-linaro \
  /home/atulk/yocto/poky-master/meta-linaro-toolchain \
  "
And local.conf MACHINE ??= "genericarmv8"
But while building bitbake with meta-toolchain for aarch64 support, I am
getting error as “ERROR: Layer 'linaro' depends on layer
'networking-layer', but this layer is not enabled in your configuration”.
Do you have any comments about building the same.
Also please note that I don’t need any external toolchain support as I wish
to build my own toolchain.

Thanks and Regards,
ATUL KUMAR SINGH
On 8 Jul 2014 19:52, "Maxin B. John"  wrote:

> Hi Atul,
>
> On Tue, Jul 08, 2014 at 07:43:03PM +0530, atulkumar singh wrote:
> > Hi Fathi and Maxin,
> >
> > Thanks as you are helping me in sorting out my issue for Aarch64 support
> in
> > meta-toolchain while building bitbake for yocto.
> > And "not working" means if we go into the machine/layer/recipes link and
> under
> > the meta-aarch64 layer the git repository link which is mention is not
> working.
> > Please let me know with your valuable suggestion.
>
> The "meta-aarch64" is present in "meta-linaro" repository.
> Clone meta-linaro :
>
> # git clone git://git.linaro.org/openembedded/meta-linaro.git
> # cd meta-linaro/meta-aarch64
>
> > Thanks and regards,
> > Atul
> >
> > On 8 Jul 2014 18:14, "Fathi Boudra"  wrote:
> >
> > On 8 July 2014 13:27, atulkumar singh 
> wrote:
>
> Best Regards,
> Maxin
> 
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

[Bruce Ashfield]

On 14-07-09 05:38 AM, Dr. Markus Eich wrote:

Dear all,

I work on the process to compile odroid xu kernel with yocto/bitbake

In the kernel sources (from hardkernel) I have the corresponding
defconfig file, i.e. in the git folder
/arch/arm/configs/odroidxu_ubuntu_defconfig.

How can I tell bitbake in my recipe to use "odroidxu_ubuntu_defconfig"?


To trigger the oe-core kernel processing to use the defconfig, you need
to put that defconfig in your SRC_URI.

Which means you should grab a copy of that from the kernel tree, and
in the same directory structure as your kernel recipe.

See meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb for an
example.

Cheers,

Bruce




My recipe looks as follow:

===
require recipes-kernel/linux/linux-yocto.inc

KERNEL_IMAGETYPE = "uImage"

COMPATIBLE_MACHINE = "odroid-xu"

LINUX_VERSION = "3.4.91"
LINUX_VERSION_EXTENSION = "-custom"

FILESEXTRAPATHS_prepend := "${THISDIR}/linux-hardkernel-3.4:"

S = "${WORKDIR}/git"

# from where to fetch the kernel
KERNEL_REPO_OWNER ??= "hardkernel"
KERNEL_REPO_URI ??= "git://github.com/${KERNEL_REPO_OWNER}/linux.git"
KBRANCH = "odroidxu-3.4.y"

SRCREV = "${AUTOREV}"

KV = "3.4.91"
PV = "${KV}+gitr${SRCPV}"
LOCALVERSION ?= ""


SRC_URI = " \
   ${KERNEL_REPO_URI};nocheckout=1;branch=${KBRANCH} \
"

PACKAGES =+ "kernel-headers"
FILES_kernel-headers = "${exec_prefix}/src/linux*"
===

Cheers,

Markus






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

Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

[Dr. Markus Eich]

bitbake -e produces the following output. I have listed the methods 
dealing with .config.




do_kernel_configme() {
echo "[INFO] doing kernel configme"
export KMETA=${KMETA}

if [ -n ${KCONFIG_MODE} ]; then
configmeflags=${KCONFIG_MODE}
else
# If a defconfig was passed, use =n as the baseline, which is 
achieved

# via --allnoconfig
if [ -f 
/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/defconfig 
]; then

configmeflags="--allnoconfig"
fi
fi

cd 
/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/git

PATH=/home/eich/yocto/poky/scripts:/home/eich/odroid/build/tmp/sysroots/x86_64-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi:/home/eich/odroid/build/tmp/sysroots/odroid-xu/usr/bin/crossscripts:/home/eich/odroid/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/eich/odroid/build/tmp/sysroots/x86_64-linux/usr/bin:/home/eich/odroid/build/tmp/sysroots/x86_64-linux/sbin:/home/eich/odroid/build/tmp/sysroots/x86_64-linux/bin:/home/eich/yocto/poky/scripts:/home/eich/yocto/poky/bitbake/bin:/home/eich/ros_catkin_ws/install_isolated/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/eich/bin:/usr/local/java/jre1.7.0_55/bin:/home/eich/install/bin:/opt/toolchains/arm-eabi-4.6/bin:/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/git/scripts/util
configme ${configmeflags} --reconfig --output 
/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/linux-odroid_xu-standard-build 
standard odroid-xu

if [ $? -ne 0 ]; then
echo "ERROR. Could not configure odroid-xu-standard"
exit 1
fi

echo "# Global settings from linux recipe" >> 
/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/linux-odroid_xu-standard-build/.config
echo "CONFIG_LOCALVERSION="\"-custom\" >> 
/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/linux-odroid_xu-standard-build/.config


}


do_compile_kernelmodules() {
unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS MACHINE
if (grep -q -i -e '^CONFIG_MODULES=y$' .config); then
oe_runmake -j 4 modules CC="arm-poky-linux-gnueabi-gcc 
-mno-thumb-interwork -marm" LD="arm-poky-linux-gnueabi-ld.bfd  "

else
bbnote "no modules to compile"
fi

}

kernel_do_configure() {
# fixes extra + in /lib/modules/2.6.37+
# $ scripts/setlocalversion . => +
# $ make kernelversion => 2.6.37
# $ make kernelrelease => 2.6.37+
touch 
/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/linux-odroid_xu-standard-build/.scmversion 
/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/git/.scmversion


# Copy defconfig to .config if .config does not exist. This allows
# recipes to manage the .config themselves in do_configure_prepend().
if [ -f 
"/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/defconfig" 
] && [ ! -f 
"/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/linux-odroid_xu-standard-build/.config" 
]; then
cp 
"/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/defconfig" 
"/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/linux-odroid_xu-standard-build/.config"

fi
eval oe_runmake_call oldnoconfig || yes '' | oe_runmake oldconfig
install -m 0644 
/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/git/arch/arm/configs/odroidxu_ubuntu_defconfig 
/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/defconfig
install -m 0644 
/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/git/arch/arm/configs/odroidxu_ubuntu_defconfig 
/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/git/.config


}


kernel_do_install() {
#
# First install the modules
#unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS MACHINE
if (grep -q -i -e '^CONFIG_MODULES=y$' .config); then
oe_runmake DEPMOD=echo 
INSTALL_MOD_PATH="/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.91+gitrAUTOINC+a26607bfa2-r0/image" 
modules_install
rm 
"/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4.9

Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

[Sathish Kumar Balasubramaniam -ERS, HCL Tech]

Sorry, Markus.
Ignore my previous post. It has error.

I think you need to check the output of "bitbake -e " and see how 
the .config file is created for your recipe.
Based on that only we need to update the recipe.

Regards,
B.Sathish Kumar

-Original Message-
From: Sathish Kumar Balasubramaniam -ERS, HCL Tech 
Sent: Wednesday, July 09, 2014 5:54 PM
To: Dr. Markus Eich; yocto@yoctoproject.org
Subject: RE: [yocto] How to select defconfig for kernel build with yocto/bitbake

Ok. Can you try the following instead of the content I gave before

KERNEL_DEFCONFIG = "odroidxu_ubuntu_defconfig"

kernel_do_configure_append() {
install -m 0644 ${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} 
${WORKDIR}/defconfig
install -m 0644 ${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} 
${S}/.config
}


Regards,
B.Sathish Kumar

-Original Message-
From: Dr. Markus Eich [mailto:markus.e...@dfki.de] 
Sent: Wednesday, July 09, 2014 5:39 PM
To: Sathish Kumar Balasubramaniam -ERS, HCL Tech; yocto@yoctoproject.org
Subject: Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

Thank you Sathish for the quick answer.

The recipes now copies odroidxu_ubuntu_defconfig to defconfig in the 
workdir, but it still seems to be ignored.
Maybe I am missing some includes to make the .config from defconfig?

Using "make odroidxu_ubuntu_defconfig" using cross compiling (followed 
by "make zImage") works fine, while bitbake virtual/kernel produces some 
errors which are probably due to the wrong .config.


Cheers,

Markus





On 09.07.2014 13:33, Sathish Kumar Balasubramaniam -ERS, HCL Tech wrote:
> Hi Markus,
>
> Try adding the following to your recipe file
>
> KERNEL_DEFCONFIG = "odroidxu_ubuntu_defconfig"
>
> do_configure_prepend() {
>  install -m 0644 ${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} 
> ${WORKDIR}/defconfig || die "No default configuration for ${MACHINE} / 
> ${KERNEL_DEFCONFIG} available."
> }
>
>
> Regards,
> B.Sathish Kumar
>
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] 
> On Behalf Of Dr. Markus Eich
> Sent: Wednesday, July 09, 2014 3:09 PM
> To: yocto@yoctoproject.org
> Subject: [yocto] How to select defconfig for kernel build with yocto/bitbake
>
> Dear all,
>
> I work on the process to compile odroid xu kernel with yocto/bitbake
>
> In the kernel sources (from hardkernel) I have the corresponding
> defconfig file, i.e. in the git folder
> /arch/arm/configs/odroidxu_ubuntu_defconfig.
>
> How can I tell bitbake in my recipe to use "odroidxu_ubuntu_defconfig"?
>
> My recipe looks as follow:
>
> ===
> require recipes-kernel/linux/linux-yocto.inc
>
> KERNEL_IMAGETYPE = "uImage"
>
> COMPATIBLE_MACHINE = "odroid-xu"
>
> LINUX_VERSION = "3.4.91"
> LINUX_VERSION_EXTENSION = "-custom"
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/linux-hardkernel-3.4:"
>
> S = "${WORKDIR}/git"
>
> # from where to fetch the kernel
> KERNEL_REPO_OWNER ??= "hardkernel"
> KERNEL_REPO_URI ??= "git://github.com/${KERNEL_REPO_OWNER}/linux.git"
> KBRANCH = "odroidxu-3.4.y"
>
> SRCREV = "${AUTOREV}"
>
> KV = "3.4.91"
> PV = "${KV}+gitr${SRCPV}"
> LOCALVERSION ?= ""
>
>
> SRC_URI = " \
> ${KERNEL_REPO_URI};nocheckout=1;branch=${KBRANCH} \
> "
>
> PACKAGES =+ "kernel-headers"
> FILES_kernel-headers = "${exec_prefix}/src/linux*"
> ===
>
> Cheers,
>
> Markus
>
>
>
>

-- 
Dr.-Ing. Markus Eich

  Senior Researcher
  Marine Inspection Robotics
  Space Robotics
  
  Besuchsadresse der Nebengeschäftstelle:
  DFKI GmbH
  Robotics Innovation Center
  Robert-Hooke-Straße 5
  28359 Bremen, Germany
  
  Postadresse der Hauptgeschäftsstelle Standort Bremen:
  DFKI GmbH
  Robotics Innovation Center
  Robert-Hooke-Straße 1
  28359 Bremen, Germany

  Tel.: +49 421 178 45-4105
  Zentrale: +49 421 178 45-0
  Fax:  +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen)
  E-Mail:   markus.e...@dfki.de

  Weitere Informationen: http://www.dfki.de/robotik
  ---
  Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
  Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
  Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
  (Vorsitzender) Dr. Walter Olthoff
  Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
  Amtsgericht Kaiserslautern, HRB 2313
  Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
  USt-Id.Nr.:DE 148646973
  Steuernummer:  19/673/0060/3
  ---



::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or in

Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

[Sathish Kumar Balasubramaniam -ERS, HCL Tech]

Ok. Can you try the following instead of the content I gave before

KERNEL_DEFCONFIG = "odroidxu_ubuntu_defconfig"

kernel_do_configure_append() {
install -m 0644 ${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} 
${WORKDIR}/defconfig
install -m 0644 ${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} 
${S}/.config
}


Regards,
B.Sathish Kumar

-Original Message-
From: Dr. Markus Eich [mailto:markus.e...@dfki.de] 
Sent: Wednesday, July 09, 2014 5:39 PM
To: Sathish Kumar Balasubramaniam -ERS, HCL Tech; yocto@yoctoproject.org
Subject: Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

Thank you Sathish for the quick answer.

The recipes now copies odroidxu_ubuntu_defconfig to defconfig in the 
workdir, but it still seems to be ignored.
Maybe I am missing some includes to make the .config from defconfig?

Using "make odroidxu_ubuntu_defconfig" using cross compiling (followed 
by "make zImage") works fine, while bitbake virtual/kernel produces some 
errors which are probably due to the wrong .config.


Cheers,

Markus





On 09.07.2014 13:33, Sathish Kumar Balasubramaniam -ERS, HCL Tech wrote:
> Hi Markus,
>
> Try adding the following to your recipe file
>
> KERNEL_DEFCONFIG = "odroidxu_ubuntu_defconfig"
>
> do_configure_prepend() {
>  install -m 0644 ${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} 
> ${WORKDIR}/defconfig || die "No default configuration for ${MACHINE} / 
> ${KERNEL_DEFCONFIG} available."
> }
>
>
> Regards,
> B.Sathish Kumar
>
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] 
> On Behalf Of Dr. Markus Eich
> Sent: Wednesday, July 09, 2014 3:09 PM
> To: yocto@yoctoproject.org
> Subject: [yocto] How to select defconfig for kernel build with yocto/bitbake
>
> Dear all,
>
> I work on the process to compile odroid xu kernel with yocto/bitbake
>
> In the kernel sources (from hardkernel) I have the corresponding
> defconfig file, i.e. in the git folder
> /arch/arm/configs/odroidxu_ubuntu_defconfig.
>
> How can I tell bitbake in my recipe to use "odroidxu_ubuntu_defconfig"?
>
> My recipe looks as follow:
>
> ===
> require recipes-kernel/linux/linux-yocto.inc
>
> KERNEL_IMAGETYPE = "uImage"
>
> COMPATIBLE_MACHINE = "odroid-xu"
>
> LINUX_VERSION = "3.4.91"
> LINUX_VERSION_EXTENSION = "-custom"
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/linux-hardkernel-3.4:"
>
> S = "${WORKDIR}/git"
>
> # from where to fetch the kernel
> KERNEL_REPO_OWNER ??= "hardkernel"
> KERNEL_REPO_URI ??= "git://github.com/${KERNEL_REPO_OWNER}/linux.git"
> KBRANCH = "odroidxu-3.4.y"
>
> SRCREV = "${AUTOREV}"
>
> KV = "3.4.91"
> PV = "${KV}+gitr${SRCPV}"
> LOCALVERSION ?= ""
>
>
> SRC_URI = " \
> ${KERNEL_REPO_URI};nocheckout=1;branch=${KBRANCH} \
> "
>
> PACKAGES =+ "kernel-headers"
> FILES_kernel-headers = "${exec_prefix}/src/linux*"
> ===
>
> Cheers,
>
> Markus
>
>
>
>

-- 
Dr.-Ing. Markus Eich

  Senior Researcher
  Marine Inspection Robotics
  Space Robotics
  
  Besuchsadresse der Nebengeschäftstelle:
  DFKI GmbH
  Robotics Innovation Center
  Robert-Hooke-Straße 5
  28359 Bremen, Germany
  
  Postadresse der Hauptgeschäftsstelle Standort Bremen:
  DFKI GmbH
  Robotics Innovation Center
  Robert-Hooke-Straße 1
  28359 Bremen, Germany

  Tel.: +49 421 178 45-4105
  Zentrale: +49 421 178 45-0
  Fax:  +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen)
  E-Mail:   markus.e...@dfki.de

  Weitere Informationen: http://www.dfki.de/robotik
  ---
  Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
  Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
  Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
  (Vorsitzender) Dr. Walter Olthoff
  Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
  Amtsgericht Kaiserslautern, HRB 2313
  Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
  USt-Id.Nr.:DE 148646973
  Steuernummer:  19/673/0060/3
  ---



::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this messag

[yocto] Installing a directory tree of files into the target filesystem

[Joe Nicholson]

 

Hi Guys 

First post on here :-) 

I'd like to create a recipe that copies a whole directory tree of files
into a directory on the output filesystem. There's nothing to build
here... it's just a web application with html files, image files, .js
files, etc. 
What would be the best way of doing this?
I can see that a small number of files and directories are installed
individually using 'install' and 'install -d', is there an equivalent
that just copies a whole tree of files into place? 

Cheers! 

Joe 

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

Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

[Dr. Markus Eich]

Thank you Sathish for the quick answer.

The recipes now copies odroidxu_ubuntu_defconfig to defconfig in the 
workdir, but it still seems to be ignored.

Maybe I am missing some includes to make the .config from defconfig?

Using "make odroidxu_ubuntu_defconfig" using cross compiling (followed 
by "make zImage") works fine, while bitbake virtual/kernel produces some 
errors which are probably due to the wrong .config.



Cheers,

Markus





On 09.07.2014 13:33, Sathish Kumar Balasubramaniam -ERS, HCL Tech wrote:

Hi Markus,

Try adding the following to your recipe file

KERNEL_DEFCONFIG = "odroidxu_ubuntu_defconfig"

do_configure_prepend() {
 install -m 0644 ${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} 
${WORKDIR}/defconfig || die "No default configuration for ${MACHINE} / 
${KERNEL_DEFCONFIG} available."
}


Regards,
B.Sathish Kumar

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Dr. Markus Eich
Sent: Wednesday, July 09, 2014 3:09 PM
To: yocto@yoctoproject.org
Subject: [yocto] How to select defconfig for kernel build with yocto/bitbake

Dear all,

I work on the process to compile odroid xu kernel with yocto/bitbake

In the kernel sources (from hardkernel) I have the corresponding
defconfig file, i.e. in the git folder
/arch/arm/configs/odroidxu_ubuntu_defconfig.

How can I tell bitbake in my recipe to use "odroidxu_ubuntu_defconfig"?

My recipe looks as follow:

===
require recipes-kernel/linux/linux-yocto.inc

KERNEL_IMAGETYPE = "uImage"

COMPATIBLE_MACHINE = "odroid-xu"

LINUX_VERSION = "3.4.91"
LINUX_VERSION_EXTENSION = "-custom"

FILESEXTRAPATHS_prepend := "${THISDIR}/linux-hardkernel-3.4:"

S = "${WORKDIR}/git"

# from where to fetch the kernel
KERNEL_REPO_OWNER ??= "hardkernel"
KERNEL_REPO_URI ??= "git://github.com/${KERNEL_REPO_OWNER}/linux.git"
KBRANCH = "odroidxu-3.4.y"

SRCREV = "${AUTOREV}"

KV = "3.4.91"
PV = "${KV}+gitr${SRCPV}"
LOCALVERSION ?= ""


SRC_URI = " \
${KERNEL_REPO_URI};nocheckout=1;branch=${KBRANCH} \
"

PACKAGES =+ "kernel-headers"
FILES_kernel-headers = "${exec_prefix}/src/linux*"
===

Cheers,

Markus






--
Dr.-Ing. Markus Eich

 Senior Researcher
 Marine Inspection Robotics
 Space Robotics
 
 Besuchsadresse der Nebengeschäftstelle:

 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 5
 28359 Bremen, Germany
 
 Postadresse der Hauptgeschäftsstelle Standort Bremen:

 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 1
 28359 Bremen, Germany

 Tel.: +49 421 178 45-4105
 Zentrale: +49 421 178 45-0
 Fax:  +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen)
 E-Mail:   markus.e...@dfki.de

 Weitere Informationen: http://www.dfki.de/robotik
 ---
 Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
 Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
 Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
 (Vorsitzender) Dr. Walter Olthoff
 Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
 Amtsgericht Kaiserslautern, HRB 2313
 Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
 USt-Id.Nr.:DE 148646973
 Steuernummer:  19/673/0060/3
 ---

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

[yocto] delete .git and .repo to check in svn

[jags gediya]

I want to check in yocto sdk on svn. so i am planning to delete all
.git and .repo directory from it. Will it create any problem in new
build after check out from svn?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

[Sathish Kumar Balasubramaniam -ERS, HCL Tech]

Hi Markus,

Try adding the following to your recipe file

KERNEL_DEFCONFIG = "odroidxu_ubuntu_defconfig"

do_configure_prepend() {
install -m 0644 ${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} 
${WORKDIR}/defconfig || die "No default configuration for ${MACHINE} / 
${KERNEL_DEFCONFIG} available."
}


Regards,
B.Sathish Kumar

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Dr. Markus Eich
Sent: Wednesday, July 09, 2014 3:09 PM
To: yocto@yoctoproject.org
Subject: [yocto] How to select defconfig for kernel build with yocto/bitbake

Dear all,

I work on the process to compile odroid xu kernel with yocto/bitbake

In the kernel sources (from hardkernel) I have the corresponding 
defconfig file, i.e. in the git folder 
/arch/arm/configs/odroidxu_ubuntu_defconfig.

How can I tell bitbake in my recipe to use "odroidxu_ubuntu_defconfig"?

My recipe looks as follow:

===
require recipes-kernel/linux/linux-yocto.inc

KERNEL_IMAGETYPE = "uImage"

COMPATIBLE_MACHINE = "odroid-xu"

LINUX_VERSION = "3.4.91"
LINUX_VERSION_EXTENSION = "-custom"

FILESEXTRAPATHS_prepend := "${THISDIR}/linux-hardkernel-3.4:"

S = "${WORKDIR}/git"

# from where to fetch the kernel
KERNEL_REPO_OWNER ??= "hardkernel"
KERNEL_REPO_URI ??= "git://github.com/${KERNEL_REPO_OWNER}/linux.git"
KBRANCH = "odroidxu-3.4.y"

SRCREV = "${AUTOREV}"

KV = "3.4.91"
PV = "${KV}+gitr${SRCPV}"
LOCALVERSION ?= ""


SRC_URI = " \
   ${KERNEL_REPO_URI};nocheckout=1;branch=${KBRANCH} \
"

PACKAGES =+ "kernel-headers"
FILES_kernel-headers = "${exec_prefix}/src/linux*"
===

Cheers,

Markus




-- 
Dr.-Ing. Markus Eich

  Senior Researcher
  Marine Inspection Robotics
  Space Robotics
  
  Besuchsadresse der Nebengeschäftstelle:
  DFKI GmbH
  Robotics Innovation Center
  Robert-Hooke-Straße 5
  28359 Bremen, Germany
  
  Postadresse der Hauptgeschäftsstelle Standort Bremen:
  DFKI GmbH
  Robotics Innovation Center
  Robert-Hooke-Straße 1
  28359 Bremen, Germany

  Tel.: +49 421 178 45-4105
  Zentrale: +49 421 178 45-0
  Fax:  +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen)
  E-Mail:   markus.e...@dfki.de

  Weitere Informationen: http://www.dfki.de/robotik
  ---
  Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
  Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
  Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
  (Vorsitzender) Dr. Walter Olthoff
  Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
  Amtsgericht Kaiserslautern, HRB 2313
  Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
  USt-Id.Nr.:DE 148646973
  Steuernummer:  19/673/0060/3
  ---

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


::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.



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

[yocto] How to select defconfig for kernel build with yocto/bitbake

[Dr. Markus Eich]

Dear all,

I work on the process to compile odroid xu kernel with yocto/bitbake

In the kernel sources (from hardkernel) I have the corresponding 
defconfig file, i.e. in the git folder 
/arch/arm/configs/odroidxu_ubuntu_defconfig.


How can I tell bitbake in my recipe to use "odroidxu_ubuntu_defconfig"?

My recipe looks as follow:

===
require recipes-kernel/linux/linux-yocto.inc

KERNEL_IMAGETYPE = "uImage"

COMPATIBLE_MACHINE = "odroid-xu"

LINUX_VERSION = "3.4.91"
LINUX_VERSION_EXTENSION = "-custom"

FILESEXTRAPATHS_prepend := "${THISDIR}/linux-hardkernel-3.4:"

S = "${WORKDIR}/git"

# from where to fetch the kernel
KERNEL_REPO_OWNER ??= "hardkernel"
KERNEL_REPO_URI ??= "git://github.com/${KERNEL_REPO_OWNER}/linux.git"
KBRANCH = "odroidxu-3.4.y"

SRCREV = "${AUTOREV}"

KV = "3.4.91"
PV = "${KV}+gitr${SRCPV}"
LOCALVERSION ?= ""


SRC_URI = " \
  ${KERNEL_REPO_URI};nocheckout=1;branch=${KBRANCH} \
"

PACKAGES =+ "kernel-headers"
FILES_kernel-headers = "${exec_prefix}/src/linux*"
===

Cheers,

Markus




--
Dr.-Ing. Markus Eich

 Senior Researcher
 Marine Inspection Robotics
 Space Robotics
 
 Besuchsadresse der Nebengeschäftstelle:

 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 5
 28359 Bremen, Germany
 
 Postadresse der Hauptgeschäftsstelle Standort Bremen:

 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 1
 28359 Bremen, Germany

 Tel.: +49 421 178 45-4105
 Zentrale: +49 421 178 45-0
 Fax:  +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen)
 E-Mail:   markus.e...@dfki.de

 Weitere Informationen: http://www.dfki.de/robotik
 ---
 Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
 Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
 Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
 (Vorsitzender) Dr. Walter Olthoff
 Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
 Amtsgericht Kaiserslautern, HRB 2313
 Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
 USt-Id.Nr.:DE 148646973
 Steuernummer:  19/673/0060/3
 ---

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

[yocto] automated hardware testing

[Robert Berger]

Hi,

I just noticed this [1] and there are rumors that in the next release
hardware testing will also work with yocto-autobuilder.

I do have a couple of boards deployer in my lab and build with
autobuilder images for them.

The consoles of my boards are connected via conservers to ethernet and I
can also remotely switch on/off power.

For the beagle bone white the setup is more complex in order to press
the reset button remotely and turn on/off the power over the USB cable
remotely.

My goal would be to build something with autobuilder, deploy to a board
and run some tests.

Is this feasible with my current infrastructure?
Can someone please guide me in the right directions.

Regards,

Robert

[1]
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto-bsp/lib/oeqa/controllers/beaglebonetarget.py...I
read the system requirements label on a software package recently. It
said "requires Windows NT or better". So I installed Unix. -- from a FAQ

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1


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

Re: [yocto] QEMU in SDK

[Joseph Andrew de la Peña]

Great! All clear now!
Thanks a lot for your help Chong!

- Joseph


On Wed, Jul 9, 2014 at 4:53 PM, Chong Lu  wrote:

>
> On 07/09/2014 04:27 PM, Joseph Andrew de la Peña wrote:
>
> Good day Chong,
>
>  Thank you so much for your input! I have also tried the ADT method you
> mentioned and saw the needed files inside download_image. Yet this is not
> the path I intended to take since in our poky, we already have our own
> generated images.
>
>  The output should be like the ADT installer where the moment you run the
> script, the images will be installed inside a certain dir in sysroots. Is
> this possible?
>
>  The expected outcome should be the moment I finished running the SDK
> script generated by populate_sdk, the images should also be seen in my sdk
> path. How can I include the images as content to the SDK script? Is there a
> variable that I need to set in conf or any?
>
>   adt-installer download images from http://adtrepo.yoctoproject.org/ ,
> maybe you can create your repo for your images.
> The script from populate_sdk can't get images default.
>
> BR
> Chong
>
>  - Joseph
>
>
> On Tue, Jul 8, 2014 at 5:54 PM, Chong Lu  wrote:
>
>>  I mean you can use adt-installer to make your sdk environment. (3.1.1.
>> Using the ADT Installer)
>> After you run adt-installer script, you can get kernel and rootfs in
>> download_image directory.
>>
>> Best Regards
>> Chong
>>
>>
>>
>> On 07/08/2014 05:39 PM, Joseph Andrew de la Peña wrote:
>>
>> Good day Chong,
>>
>>  Actually, I have used ADT (Section 3.4 Optionally Building a Toolchain
>> Installer). I used the method -c populate_sdk and it generated a toolchain
>> script from my existing build workdir's core-image-XXX. I ran the toolchain
>> and it generated a sysroots dir to /path/to/sysroots (SDK_PATH).
>>
>>  Here's the directory structure:
>> + SDK_PATH
>> --- + environment-setup-XXX
>> --- + site-config-XXX
>> --- + sysroots (dir)
>> -- + XXX-poky-linux (dir)
>> -- + XXX-pokysdk-linux (dir)
>> --- + version-XXX
>>
>>  The poky-linux dir does not contain a build dir and nowhere are the
>> images (kernel and ext3) to be found. Thus, the main problem is how can I
>> ran qemu with my SDK setup. This would lead to my sub question: since QEMU
>> needs the kernel and ext3 files, how can I automatically copy these images
>> from my existing build workdir to the newly created SDK dir.
>>
>>  Thanks,
>> Joseph
>>
>>
>>
>>
>>
>> On Tue, Jul 8, 2014 at 3:26 PM, Chong Lu  wrote:
>>
>>>  Hi Joseph,
>>>
>>> Maybe you can use adt-installer.
>>>
>>>
>>> http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html#using-the-adt-installer
>>>
>>> Best Regards
>>> Chong
>>>
>>> On 07/08/2014 02:15 PM, Joseph Andrew de la Peña wrote:
>>>
>>> Good day ALL,
>>>
>>>  I was wondering if it's possible to automatically add QEMU
>>> dependencies (kernel and ext3 files) into the script generated by
>>> do_populate_sdk? Then after running the generated SDK script, the images
>>> will reside in /path/to/sysroots/xxx-poky-xxx/tmp/images? Then just add an
>>> environment variable to the environment script to locate the images path.
>>> Is this possible?
>>>
>>>  The intention is to run QEMU in a host machine with extracted SDK. Any
>>> suggestions on other better ways to run QEMU in another machine w/ SDK
>>> would be great.
>>>
>>>  Thanks,
>>> Joseph
>>>
>>>
>>>
>>>
>>
>>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QEMU in SDK

[Chong Lu]

On 07/09/2014 04:27 PM, Joseph Andrew de la Peña wrote:

Good day Chong,

Thank you so much for your input! I have also tried the ADT method you 
mentioned and saw the needed files inside download_image. Yet this is 
not the path I intended to take since in our poky, we already have our 
own generated images.


The output should be like the ADT installer where the moment you run 
the script, the images will be installed inside a certain dir in 
sysroots. Is this possible?


The expected outcome should be the moment I finished running the SDK 
script generated by populate_sdk, the images should also be seen in my 
sdk path. How can I include the images as content to the SDK script? 
Is there a variable that I need to set in conf or any?


adt-installer download images from http://adtrepo.yoctoproject.org/ , 
maybe you can create your repo for your images.

The script from populate_sdk can't get images default.

BR
Chong

- Joseph


On Tue, Jul 8, 2014 at 5:54 PM, Chong Lu > wrote:


I mean you can use adt-installer to make your sdk environment.
(3.1.1. Using the ADT Installer)
After you run adt-installer script, you can get kernel and rootfs
in download_image directory.

Best Regards
Chong



On 07/08/2014 05:39 PM, Joseph Andrew de la Peña wrote:

Good day Chong,

Actually, I have used ADT (Section 3.4 Optionally Building a
Toolchain Installer). I used the method -c populate_sdk and it
generated a toolchain script from my existing build workdir's
core-image-XXX. I ran the toolchain and it generated a sysroots
dir to /path/to/sysroots (SDK_PATH).

Here's the directory structure:
+ SDK_PATH
--- + environment-setup-XXX
--- + site-config-XXX
--- + sysroots (dir)
-- + XXX-poky-linux (dir)
-- + XXX-pokysdk-linux (dir)
--- + version-XXX

The poky-linux dir does not contain a build dir and nowhere are
the images (kernel and ext3) to be found. Thus, the main problem
is how can I ran qemu with my SDK setup. This would lead to my
sub question: since QEMU needs the kernel and ext3 files, how can
I automatically copy these images from my existing build workdir
to the newly created SDK dir.

Thanks,
Joseph





On Tue, Jul 8, 2014 at 3:26 PM, Chong Lu mailto:chong...@windriver.com>> wrote:

Hi Joseph,

Maybe you can use adt-installer.


http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html#using-the-adt-installer

Best Regards
Chong

On 07/08/2014 02:15 PM, Joseph Andrew de la Peña wrote:

Good day ALL,

I was wondering if it's possible to automatically add QEMU
dependencies (kernel and ext3 files) into the script
generated by do_populate_sdk? Then after running the
generated SDK script, the images will reside in
/path/to/sysroots/xxx-poky-xxx/tmp/images? Then just add an
environment variable to the environment script to locate the
images path. Is this possible?

The intention is to run QEMU in a host machine with
extracted SDK. Any suggestions on other better ways to run
QEMU in another machine w/ SDK would be great.

Thanks,
Joseph










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

Re: [yocto] QEMU in SDK

[Joseph Andrew de la Peña]

Good day Chong,

Thank you so much for your input! I have also tried the ADT method you
mentioned and saw the needed files inside download_image. Yet this is not
the path I intended to take since in our poky, we already have our own
generated images.

The output should be like the ADT installer where the moment you run the
script, the images will be installed inside a certain dir in sysroots. Is
this possible?

The expected outcome should be the moment I finished running the SDK script
generated by populate_sdk, the images should also be seen in my sdk path.
How can I include the images as content to the SDK script? Is there a
variable that I need to set in conf or any?

- Joseph


On Tue, Jul 8, 2014 at 5:54 PM, Chong Lu  wrote:

>  I mean you can use adt-installer to make your sdk environment. (3.1.1.
> Using the ADT Installer)
> After you run adt-installer script, you can get kernel and rootfs in
> download_image directory.
>
> Best Regards
> Chong
>
>
>
> On 07/08/2014 05:39 PM, Joseph Andrew de la Peña wrote:
>
> Good day Chong,
>
>  Actually, I have used ADT (Section 3.4 Optionally Building a Toolchain
> Installer). I used the method -c populate_sdk and it generated a toolchain
> script from my existing build workdir's core-image-XXX. I ran the toolchain
> and it generated a sysroots dir to /path/to/sysroots (SDK_PATH).
>
>  Here's the directory structure:
> + SDK_PATH
> --- + environment-setup-XXX
> --- + site-config-XXX
> --- + sysroots (dir)
> -- + XXX-poky-linux (dir)
> -- + XXX-pokysdk-linux (dir)
> --- + version-XXX
>
>  The poky-linux dir does not contain a build dir and nowhere are the
> images (kernel and ext3) to be found. Thus, the main problem is how can I
> ran qemu with my SDK setup. This would lead to my sub question: since QEMU
> needs the kernel and ext3 files, how can I automatically copy these images
> from my existing build workdir to the newly created SDK dir.
>
>  Thanks,
> Joseph
>
>
>
>
>
> On Tue, Jul 8, 2014 at 3:26 PM, Chong Lu  wrote:
>
>>  Hi Joseph,
>>
>> Maybe you can use adt-installer.
>>
>>
>> http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html#using-the-adt-installer
>>
>> Best Regards
>> Chong
>>
>> On 07/08/2014 02:15 PM, Joseph Andrew de la Peña wrote:
>>
>> Good day ALL,
>>
>>  I was wondering if it's possible to automatically add QEMU dependencies
>> (kernel and ext3 files) into the script generated by do_populate_sdk? Then
>> after running the generated SDK script, the images will reside in
>> /path/to/sysroots/xxx-poky-xxx/tmp/images? Then just add an environment
>> variable to the environment script to locate the images path. Is this
>> possible?
>>
>>  The intention is to run QEMU in a host machine with extracted SDK. Any
>> suggestions on other better ways to run QEMU in another machine w/ SDK
>> would be great.
>>
>>  Thanks,
>> Joseph
>>
>>
>>
>>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto