Re: [yocto] Navigating the layer labyrinth

[Aaron Schwartz]

 Hello,

I am not sure if you've found the OpenEmbedded Layer Index [0] yet, but
that's a good resource and an example of what can be done.  I believe the
source code is available [1] and I've toyed with the idea of getting it
working locally (although I've not had the time to do so).

That could be a part of what you're looking for, at least.

Hope that helps,
Aaron



0) https://layers.openembedded.org/layerindex/branch/master/recipes/
1) http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/tree/layerindex


On Thu, Oct 12, 2017 at 5:34 AM, Bernd  wrote:

> I am a new user for a few weeks now, trying to make a customized image
> for a toradex colibri-vf module, so far I have succeeded in the
> following disciplines:
>
> * adding the 3rd party layers that I need
> * making my own layers
> * using a .bbappend to patch the device tree
> * using a .bbappend to workaround a bug(?) in one of the freescale layers
> * writing my own recipe to install a python script
> * writing recipes for pulling additional python packages with pypi and
> setuptools3
> * writing my own image recipe
> * making it boot and run on the target platform
>
> During this learning experience I have made the following observations
> of circumstances that made it especially hard for me to get things
> done, I'm not yet really sure if this is a documentation issue or if
> it is really a missing feature but I feel I could have had a much
> *much* easier time learning and understanding the concepts and
> relationships and the inner workings of existing layers upon which I
> want to build my system if the following things were possible (and/or
> if they are already possible they should be documented in the very
> first chapter of the documentation):
>
> * Finding the *file path* of an existing recipe (or append file or
> class) *by its name* and also all existing .bbappends for it, i
> imagine something simple like bitbake --show-paths foo-bar would
> output me the small list of absolute paths of recipe files by the name
> foo-bar and all matching .bbappend files in the order in which they
> would be applied, it would show me only this small list of paths and
> not dump 100kb of unrelated information along with it. This would be
> incredibly helpful when I need to inspect an existing recipe in order
> to understand how I can bbappend it or even just to see and understand
> what it actually does.
>
> * A simple way to track the assignment of a certain variable, to
> inspect its contents and if it refers to other variables then
> recursively show their contents too (and also the path of the bb file
> where this happens), and also show which other recipes will directly
> and indirectrly depend on this variable further down the line, I
> imagine this should output two tree-like structures where one can see
> at one glance how and where all the contents of that variable come
> from and where they are going to be used. Again this should be a
> simple command that formats and outputs that (and only that)
> information in a well formatted and compact tree-like representation.
>
> * The absolute killer application would be an IDE or an editor plugin
> where I open any .bb file and can then just CTRL-click on any include,
> require, inherit, depend, rdepend, or any variable name and it would
> open another editor containing that recipe file where it is defined
> and/or populate a sidebar with a list or a tree of direct and indirect
> references to that name, backward and forward, and I could just click
> on any node of that tree an and it would open the file in the editor
> and jump to that line of code. Such a thing would be an incredibly
> helpful tool, it would make even the most complex and tangled
> labyrinth of recipes navigable with ease.
>
> Please tell me that such a thing already exists and I just have not
> found it yet.
>
> Bernd
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 

Aaron Schwartz
Production
Logic Supply
Direct: +1 802 861 2300 Ext. 530
Main: +1 802 861 2300
www.logicsupply.com

Google+ <https://plus.google.com/+Logicsupply/posts> | Twitter
<https://twitter.com/logicsupply> | LinkedIn
<https://www.linkedin.com/company/logic-supply> | YouTube
<https://www.youtube.com/user/logicsupply>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RFC: autotooler: generation of "configure.ac" and "Makefile.am" using Kconfig

[Aaron Schwartz]

sl   Include OpenSSL],
> [case "${enableval}" in
> yes)use_openssl=true  ;;
> no) use_openssl=false ;;
> *) AC_MSG_ERROR(bad value ${enableval} for
> --enable-openssl) ;;
>  esac
> ],
> [use_openssl=false])
> AM_CONDITIONAL(CONFIG_OPENSSL, test x$openssl = xtrue)
>
> #  Pthread Libraries
> AC_ARG_WITH([pthread-include-path],
> [AS_HELP_STRING([--with-pthread-include-path],[location of the
> PThread headers, defaults to /usr/include])],
> [CFLAGS_PTHREAD="-I$withval"],
> [CFLAGS_PTHREAD="-I/usr/include"])
> AC_SUBST([PTHREAD_CFLAGS])
>
> AC_ARG_WITH([pthread-lib-path],
> [AS_HELP_STRING([--with-pthread-lib-path],[location of the
> PThread libraries, defaults to /usr/include])],
> [PTHREAD_LIBS="-L$withval" -lpthread],
> [PTHREAD_LIBS="-L/usr/include -lpthread"])
> AC_SUBST([PTHREAD_LIBS])
>
> AC_ARG_ENABLE(pthread,
> [--enable-pthread   Include PThreads],
>     [case "${enableval}" in
> yes)use_pthread=true  ;;
> no) use_pthread=false ;;
> *) AC_MSG_ERROR(bad value ${enableval} for
> --enable-pthread) ;;
>  esac
> ],
> [use_pthread=false])
> AM_CONDITIONAL(CONFIG_PTHREAD, test x$pthread = xtrue)
>
> #  Debug
> AC_ARG_ENABLE(debug,
> [--enable-debug Build with DEBUG enabled],
> [case "${enableval}" in
> yes)debug=true  ;;
> no) debug=false ;;
> *) AC_MSG_ERROR(bad value ${enableval} for --enable-debug)
> ;;
>  esac
> ],
> [debug=false])
> AM_CONDITIONAL(CONFIG_DEBUG, test x$debug = xtrue)
>
> AC_ARG_ENABLE(examples,
> [--enable-examples  Build examples],
> [case "${enableval}" in
> yes)examples=true  ;;
> no) examples=false ;;
> *) AC_MSG_ERROR(bad value ${enableval} for
> --enable-examples) ;;
>  esac
> ],
> [examples=false])
> AM_CONDITIONAL(CONFIG_EXAMPLES, test x$examples = xtrue)
>
> AC_SUBST([CFLAGS])
> AC_CONFIG_FILES([Makefile  libyocto.pc])
> AC_OUTPUT
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 

Aaron Schwartz
Production
Logic Supply
Direct: +1 802 861 2300 Ext. 530
Main: +1 802 861 2300
www.logicsupply.com

Google+ <https://plus.google.com/+Logicsupply/posts> | Twitter
<https://twitter.com/logicsupply> | LinkedIn
<https://www.linkedin.com/company/logic-supply> | YouTube
<https://www.youtube.com/user/logicsupply>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how to execute bitbake menuconfig from ssh server

[Aaron Schwartz]

Tmux [0] also works well for this, and I've never tried it with Screen (a
similar utility) so here's instructions using Tmux:

You need to install Tmux on the server you are using SSH to connect to,
then as soon as you SSH into the server run `$ tmux`.  Then when you run `$
bitbake -c menuconfig ...` it will automatically open a second pane on the
bottom half of your screen where you can edit your kernel config.  That
pane will close automatically when you exit the menuconfig application.

I hope that helps!
Aaron


0)  https://github.com/tmux/tmux/wiki

On Wed, Sep 13, 2017 at 7:17 AM, yahia farghaly 
wrote:

>
> can you give some steps on how to do this ?
>
>
> ‌
>
> On 13 September 2017 at 10:54, Yusuke Mitsuki <
> mickey.happygolu...@gmail.com> wrote:
>
>> Hello
>>
>> You can use screen.
>> If your host is ubuntu,you can get via apt as follows.
>>
>> sudo apt install screen.
>>
>> If necessary , you can set auto or screen to OE_TERMINAL environment.
>>
>> 2017/09/13 16:09 "yahia farghaly" :
>>
>>> Hi,
>>>
>>> I am working with yocto from a remote server using ssh. i want to
>>> execute *bitbake -c menuconfig virtual/kernel*  . It fails to open
>>> since it tries to open another shell.
>>> how can i redirect output of menuconfig to my current ssh session ?
>>>
>>> --
>>> Yahia Farghaly
>>> Graduated from Faculty of Engineering - Electronics and Communications
>>> Department at Cairo University.
>>> Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub
>>> <https://github.com/yahiafarghaly>
>>>
>>>
>>>
>>> ‌
>>>
>>> --
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>>
>
>
> --
> Yahia Farghaly
> Graduated from Faculty of Engineering - Electronics and Communications
> Department at Cairo University.
> Linkedin <https://linkedin.com/in/yahiafarghaly> - GitHub
> <https://github.com/yahiafarghaly>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>


-- 

Aaron Schwartz
Production
Logic Supply
Direct: +1 802 861 2300 Ext. 530
Main: +1 802 861 2300
www.logicsupply.com

Google+ <https://plus.google.com/+Logicsupply/posts> | Twitter
<https://twitter.com/logicsupply> | LinkedIn
<https://www.linkedin.com/company/logic-supply> | YouTube
<https://www.youtube.com/user/logicsupply>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Predictable network interface names without systemd?

[Aaron Schwartz]

Wow, thanks Chris and Andre!

I'm just getting to play around with this, but Andre's trick seems to have
worked exactly like I was hoping for.  I ended up just adding a bbappend
that removes the file touched in the line of the eudev recipe Andre
referenced.

Thanks again,
Aaron

On Fri, Aug 18, 2017 at 4:59 PM, Andre McCurdy  wrote:

> On Fri, Aug 18, 2017 at 9:37 AM, Aaron Schwartz
>  wrote:
> > Does anybody here know of a way to get predictable network interface
> names
> > without systemd?
>
> If you are using eudev, then try commenting out the line below "Use
> classic network interface naming scheme" in the eudev recipe.
>
> > I realize I could write a script to do it myself, but I was hoping
> there's
> > an easier solution that's ready to go (or close to it).
> >
> > Thanks in advance!
> > Aaron
> >
> > --
> > ___
> > 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] Predictable network interface names without systemd?

[Aaron Schwartz]

Does anybody here know of a way to get predictable network interface names

without systemd?

I realize I could write a script to do it myself, but I was hoping there's
an easier solution that's ready to go (or close to it).

Thanks in advance!
Aaron
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to have Poky automatically login at boot?

[Aaron Schwartz]

Good tip Andre!

Just adding 'auto-serial-console' to IMAGE_INSTALL results in openvt
complaining that VT1 is already in use and then the user is presented with
the regular login.  It looks like I'll be able to make this work once I
figure out how to disable whatever's claiming that vty, though.

Thanks for the help

On Fri, Jul 28, 2017 at 8:32 PM, Andre McCurdy  wrote:

> On Fri, Jul 28, 2017 at 11:29 AM, Aaron Schwartz
>  wrote:
> > Hello,
> >
> > I'm trying to have the busybox getty in Poky login as root automatically
> but
> > I can't seem to get it working.
>
> This may be a possible solution:
>
>   https://git.linaro.org/openembedded/meta-linaro.git/
> tree/meta-linaro/recipes-linaro/auto-serial-console/
> auto-serial-console_0.1.bb
>
> > So far I have a sysvinit-inittab_2.%.bbappend:
> >>
> >> PR := "${PR}.1"
> >> SYSVINIT_ENABLED_GETTYS="1 2 3 4"
> >> do_install() {
> >> install -d ${D}${sysconfdir}
> >> install -m 0644 ${WORKDIR}/inittab ${D}${sysconfdir}/inittab
> >> install -d ${D}${base_bindir}
> >> install -m 0755 ${WORKDIR}/start_getty
> ${D}${base_bindir}/start_getty
> >> set -x
> >> tmp="${SERIAL_CONSOLES}"
> >> for i in $tmp
> >> do
> >> j=`echo ${i} | sed s/\;/\ /g`
> >> l=`echo ${i} | sed -e 's/tty//' -e 's/^.*;//' -e 's/;.*//'`
> >> label=`echo $l | sed 's/.*\(\)/\1/'`
> >> echo "$label:12345:respawn:${base_bindir}/start_getty ${j} vt102" >>
> >> ${D}${sysconfdir}/inittab
> >> done
> >> if [ "${USE_VT}" = "1" ]; then
> >> cat <>${D}${sysconfdir}/inittab
> >> # ${base_sbindir}/getty invocations for the runlevels.
> >> #
> >> # The "id" field MUST be the same as the last
> >> # characters of the device (after "tty").
> >> #
> >> # Format:
> >> #  :::
> >> #
> >> EOF
> >> for n in ${SYSVINIT_ENABLED_GETTYS}
> >> do
> >> echo "$n:12345:respawn:${base_sbindir}/mingetty --autologin
> >> root 38400 tty$n" >> ${D}${sysconfdir}/inittab
> >> done
> >> echo "" >> ${D}${sysconfdir}/inittab
> >> fi
> >> }
> >
> >
> > I have tried a number of flags with the default getty, including using a
> > shell as login.  I tried adding mingetty to my image to see if that would
> > work with it's "--autologin" flag, but I still got the busybox getty
> yelling
> > at me about unrecognized flags.
> >
> > Is the best approach to adjust the ALTERNATIVE_PRIORITY for either the
> > busybox getty or mingetty to have update-alternatives select mingetty,
> or is
> > there an easier modification to my sysvinit-innittab bbappend above that
> > will enable autologin?
> >
> > Thanks for the help!
> > Aaron
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>



-- 

Aaron Schwartz
Production
Logic Supply
Direct: +1 802 861 2300 Ext. 530
Main: +1 802 861 2300
www.logicsupply.com

Google+ <https://plus.google.com/+Logicsupply/posts> | Twitter
<https://twitter.com/logicsupply> | LinkedIn
<https://www.linkedin.com/company/logic-supply> | YouTube
<https://www.youtube.com/user/logicsupply>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to have Poky automatically login at boot?

[Aaron Schwartz]

Hello,

I'm trying to have the busybox getty in Poky login as root automatically
but I can't seem to get it working.

So far I have a sysvinit-inittab_2.%.bbappend:

> PR := "${PR}.1"
> SYSVINIT_ENABLED_GETTYS="1 2 3 4"
> do_install() {
> install -d ${D}${sysconfdir}
> install -m 0644 ${WORKDIR}/inittab ${D}${sysconfdir}/inittab
> install -d ${D}${base_bindir}
> install -m 0755 ${WORKDIR}/start_getty ${D}${base_bindir}/start_getty
> set -x
> tmp="${SERIAL_CONSOLES}"
> for i in $tmp
> do
> j=`echo ${i} | sed s/\;/\ /g`
> l=`echo ${i} | sed -e 's/tty//' -e 's/^.*;//' -e 's/;.*//'`
> label=`echo $l | sed 's/.*\(\)/\1/'`
> echo "$label:12345:respawn:${base_bindir}/start_getty ${j} vt102" >>
> ${D}${sysconfdir}/inittab
> done
> if [ "${USE_VT}" = "1" ]; then
> cat <>${D}${sysconfdir}/inittab
> # ${base_sbindir}/getty invocations for the runlevels.
> #
> # The "id" field MUST be the same as the last
> # characters of the device (after "tty").
> #
> # Format:
> #  :::
> #
> EOF
> for n in ${SYSVINIT_ENABLED_GETTYS}
> do
> echo "$n:12345:respawn:${base_sbindir}/mingetty --autologin
> root 38400 tty$n" >> ${D}${sysconfdir}/inittab
> done
> echo "" >> ${D}${sysconfdir}/inittab
> fi
> }


I have tried a number of flags with the default getty, including using a
shell as login.  I tried adding mingetty to my image to see if that would
work with it's "--autologin" flag, but I still got the busybox getty
yelling at me about unrecognized flags.

Is the best approach to adjust the ALTERNATIVE_PRIORITY for either the
busybox getty or mingetty to have update-alternatives select mingetty, or
is there an easier modification to my sysvinit-innittab bbappend above that
will enable autologin?

Thanks for the help!
Aaron
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto