[yocto] External Build

Hello everyone, I am a novice to Linux and poky and I am having a bit of a challenge with completing the quickstart steps. I have installed poky on my host computer but I want to install the build directory on an external harddrive. Every time I run through the steps I run into an error, no

Re: [yocto] External Build

Hi, Just to clarify things, what do you call "poky" and what do you call "the build"? I am interested by the answer to this one ... Le ven. 23 oct. 2015 à 20:01, a écrit : > Hello everyone, > > I am a novice to Linux and poky and I am having a bit of a challenge with

[yocto] Turn off X screen blanking

I am trying to disable screen blanking in X by default. This bug talks about doing the same thing but it is not currently completed: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7278 I am using "dizzy" for compatibility with the meta-amd layer. I found the xserver-common recipe in meta-oe

Re: [yocto] External Build

On 23 October 2015 at 19:00, wrote: > install the build directory on an external harddrive. Every time I run > through the steps I run into an error, no matter what I do. > What steps did you make to do the build on the external drive, and what was the error? Simply

Re: [yocto] External Build

On 10/23/2015 11:35 AM, Valentin Le bescond wrote: > Hi, > > Just to clarify things, what do you call "poky" and what do you call "the > build"? > > I am interested by the answer to this one ... Poky is the Yocto Project reference distribution. OpenEmbedded is the build system. Philip > >

Re: [yocto] Alternate Terminal

> FYI you can find an xterm recipe in meta-oe: > Thanks that is exactly what I was looking for. -Daniel Smith This message and any enclosures are intended only for the addressee. Please notify the sender by email if you are not the intended recipient. If you are not the intended

[yocto] Yocto Project Status WW43

Current Dev Position: YP 2.0 Final (rc2 is in QA) Next Deadline: YP 2.0 Final Release Target: Oct. 30, 2015 (We will miss this date.) SWAT team rotation: Benjamin -> Juro https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Top Bugs to be tackled (2.0 release blockers): *

[yocto] Disabling ipv6

Hello, We're trying to disable ipv6 in our build and are able to do so by directly editing the file meta/conf/distro/include/default-distrovars.inc and deleting "ipv6" from "DISTRO_FEATURES_LIBC_DEFAULT ?= "ipv4 ipv6 libc-backtrace lib..." Is there a better way to disable ipv6 so that we can do

Re: [yocto] Disabling ipv6

On 24 October 2015 at 00:28, Todd Efflam wrote: > We're trying to disable ipv6 in our build and are able to do so by > directly editing the file > meta/conf/distro/include/default-distrovars.inc and deleting "ipv6" > from "DISTRO_FEATURES_LIBC_DEFAULT ?= "ipv4 ipv6

[yocto] Packaging an externally built library?

I have an externally built library (libcdpfsw.so) that I am trying to install in my image. The library is written in Ada, so it is built using an external Ada compiler. I've tested it on the target and it works, but I'd like it to be installed in my image. I verified that the do_install

Re: [yocto] Packaging an externally built library?

On 23 October 2015 at 23:05, Smith, Daniel W wrote: > If I look through the packaging logs it looks like it attampts to create a > bunch of different packages (cdp-fsw, cdp-fsw-dbg, cdp-fsw-dev, > cdp-fsw-doc, cdp-fsw-locale) but most of them end up being empty except >

Re: [yocto] Packaging an externally built library?

FILES_${PN} += " ${libdir}/*.so" If I look through the packaging logs it looks like it attampts to create a bunch of different packages (cdp-fsw, cdp-fsw-dbg, cdp-fsw-dev, cdp-fsw-doc, cdp-fsw-locale) but most of them end up being empty except cdp-fsw-dev. Then if I look through the RPMs

Re: [yocto] Alternate Terminal

Hi Daniel, On Thursday 22 October 2015 22:18:12 Smith, Daniel W wrote: > Does anyone know of an easy way to install xterm, gnome-terminal, or Konsole > on Yocto. I need a terminal window that has a -e option to execute a > program in the shell, which matchbox-terminal appears to not support.