On Monday 16 September 2013 23:16:51 Khem Raj wrote:
> On Sep 16, 2013, at 10:54 PM, Rohit2 Jindal
> wrote:
> > Please suggest me the way to git clone from two repos parallel in the same
> > recipe Is possible in yocto .If yes how to do that. Eg
> > SRC_URI =
> > "git://ep-code.xyz.com/sysconfig.g
On Tuesday 17 September 2013 14:28:36 Rohit2 Jindal wrote:
> The way you mentioned to put option inSRC_URI doesnot work it allows to
> download first repository in SRC_URI and gives error not allowing to
> download Second one. Gives error branch checkout id is not a valid id for
> second src_uri.
>
We are using a user defined distro, based on poky-tiny. That is, we
'require' poky-tiny.conf.
It is done this way in order not clutter our distro configuration with
too much magics and defaults.
However, one problem now is that poky-tiny also 'require' poky.conf,
and implicitly is doing
DISTRO_FEA
Hi,
SRC_URI =
"git://ep-code.xtz.com/u-boot.git;branch=xxx-ep-20130823-3.0-alpha;protocol=ssh;subpath=uboot"
SRC_URI =
"git://ep-code.xtz.com/x-load.git;branch=xxx-ep-20130823-3.0-alpha;protocol=ssh;subpath=xload"
Regards,
Rohit Jindal
-Original Message-
From: Paul Eggleton [mailto:pa
On Tuesday 17 September 2013 14:35:53 Rohit2 Jindal wrote:
> SRC_URI =
> "git://ep-code.xtz.com/u-boot.git;branch=xxx-ep-20130823-3.0-alpha;protocol
> =ssh;subpath=uboot" SRC_URI =
> "git://ep-code.xtz.com/x-load.git;branch=xxx-ep-20130823-3.0-alpha;protocol
> =ssh;subpath=xload"
There are sever
Hello
Task #9 - How to add bad/ugly:
https://community.freescale.com/docs/DOC-95254
Thanks Daiane,
jose
PD: search keywords: yocto gstreamer bad ugly
El 16/09/2013 18:14, Jose Mª Ferreiro escribió:
Hello
Here is: iMX6 Sabre Lite + Yocto dylan
We want to reproduce some music and video file
On Tue, Sep 17, 2013 at 11:04 AM, Hans Beckérus wrote:
> We are using a user defined distro, based on poky-tiny. That is, we
> 'require' poky-tiny.conf.
> It is done this way in order not clutter our distro configuration with
> too much magics and defaults.
> However, one problem now is that poky-
On Tue, Sep 17, 2013 at 12:15 PM, Hans Beckérus wrote:
> > The resulting DISTRO_FEATURES (as checked by bitbake -e) shows that
> > everything appended by poky is also added to the custom distro.
> > Now, we would like to remove everything but the large file support as
> > added by poky. How do we
I am trying to debug the kernel through kgdb for an imx6 sabre lite board with
the following kernel built from poky 1.4:
root@imx6qsabrelite:~# uname -a
Linux imx6qsabrelite 3.0.35-1.1.0+g2dc5560 #1 SMP PREEMPT Thu Aug 8 15:15:39
CEST 2013 armv7l GNU/Linux
The system boot well but when I try to
All,
I have an image that is based upon core-image-minimal (build poky/dylan-9.0.1)
with a few extra packages. In total, 'opkg list-installed' on my target system
shows about 100 packages installed. I am using the tmp/deploy/ipk directory as
I have built as a basis for firmware upgrade for my
Hello Giuseppe,
On 17-Sep-13, BITONTI Giuseppe (MM) wrote:
> I am trying to debug the kernel through kgdb for an imx6 sabre lite board
> with the following kernel built from poky 1.4:
>
> root@imx6qsabrelite:~# uname -a
> Linux imx6qsabrelite 3.0.35-1.1.0+g2dc5560 #1 SMP PREEMPT Thu Aug 8 15:15:
Thanks Apelete for your help, but the command you suggested returns the
following:
root@imx6qsabrelite:~# cat /sys/module/kgdboc/parameters/kgdboc
cat: can't open '/sys/module/kgdboc/parameters/kgdboc': No such file or
directory
root@imx6qsabrelite:~# echo ttymxc1,115200 >
/sys/module/kgdboc/p
On 17-Sep-13, Apelete Seketeli wrote:
> Hello Giuseppe,
>
> On 17-Sep-13, BITONTI Giuseppe (MM) wrote:
> > I have configured the kernel with the command:
> >
> > bitbake -c menuconfig linux-imx
> >
> > enabling:
> >
> > -*- Magic SysRq key
> > [*] Kernel debugging
> > [*] Compile the kernel wit
On 17-Sep-13, BITONTI Giuseppe (MM) wrote:
> Thanks Apelete for your help, but the command you suggested returns the
> following:
>
> root@imx6qsabrelite:~# cat /sys/module/kgdboc/parameters/kgdboc
> cat: can't open '/sys/module/kgdboc/parameters/kgdboc': No such file or
> directory
>
> root@im
Thank you, I solved it.
It was my mistake, I was modifing the wrong defconfig file.
Regards,
Giuseppe
-Messaggio originale-
Da: Apelete Seketeli [mailto:apel...@seketeli.net]
Inviato: martedì 17 settembre 2013 16:12
A: BITONTI Giuseppe (MM)
Cc: yocto@yoctoproject.org
Oggetto: Re: R: [yoc
bc-posix-regexp
libc-inet libc-nis sysvinit largefile nfs"
Build Configuration:
BB_VERSION= "1.19.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "SUSE-LINUX-11"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE = "zynq-zc
Hi Brad,
On Tuesday 17 September 2013 17:48:18 Brad Litterell wrote:
> I've been using externalsrc for a few days now and have a follow on
> question.
>
> It appears that bitbake's state information for the various recipes doesn't
> react to changes in source files in an external source. IOW, wh
Thank you!
I've been using externalsrc for a few days now and have a follow on question.
It appears that bitbake's state information for the various recipes doesn't
react to changes in source files in an external source. IOW, when I change a
file in my external folder I need to perform 3 steps
${DISTRO_FEATURES_WIFI}
> libc-libm libc-crypt libc-utmp libc-getlogin libc-posix-regexp
> libc-inet libc-nis sysvinit largefile nfs"
>
> Build Configuration:
> BB_VERSION = "1.19.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING
I have a number of QT components that have qmake style .pro files.
In my recipe I inherit both externalsrc & qmake2. I'm using qmake2 based on
the quicky sample recipe since I don't need X11 or the other GUI libraries.
In the bitbake work folder, the generated run.do_configure script resembles
All,
We attempted a spin of rc2 today and found issues that make it
necessary for an rc3 spin which will probably happen tomorrow
afternoon PST. We are going to let the build continue so that we can
identify any other issues, but so far, the main issue seems to be
libxml-parser-perl qa check compl
This patch is pretty straight forward: All we do is call the
'install-headers' make target at the end of do_install. We then add
the interface 'include' directory to the dev package. This allows
projects that ship their own SELinux policy (not in the refpolicy)
to build against the refpolicy header
22 matches
Mail list logo
