Hi All,
I am creating a new recipe in bsp layer. So I created a bb file inside the
recipe.
Then from the build directory, I am able to successfully compile the source
files and was able to create the library ( bitbake -c compile -f
). This is a makefile based package and I don't have an instal
Am 08.11.2014 13:10 schrieb "hari kumar" :
>
> Hi All,
>
> I am creating a new recipe in bsp layer. So I created a bb file inside
the recipe.
> Then from the build directory, I am able to successfully compile the
source files and was able to create the library ( bitbake -c compile -f
). This is a
Am 07.11.2014 um 12:55 schrieb Burton, Ross :
> Hi Wolfgang,
>
> On 5 November 2014 19:29, Wolfgang Denk wrote:
> meta/recipes-devtools/perl/perl-native_5.14.3.bb | 4 ++--
> meta/recipes-devtools/perl/perl_5.14.3.bb| 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> Perl w
So I am using core-image-minimal and trying to shrink things as much as
possible for boot speed. I wrap the bitbake command in some other
commands to basically extract the image and then attach it to a kernel
as a ramdisk. So the size of the image is critical to boot speed.
In some of my custo
On Nov 8, 2014 9:02 AM, "Dean" wrote:
>
> So I am using core-image-minimal and trying to shrink things as much as
possible for boot speed. I wrap the bitbake command in some other commands
to basically extract the image and then attach it to a kernel as a ramdisk.
So the size of the image is criti
On Nov 8, 2014 9:23 AM, "Brian Hutchinson" wrote:
>
>
> On Nov 8, 2014 9:02 AM, "Dean" wrote:
> >
> > So I am using core-image-minimal and trying to shrink things as much as
possible for boot speed. I wrap the bitbake command in some other commands
to basically extract the image and then attach i
On 8 November 2014 14:23, Brian Hutchinson wrote:
> I'm planning to just start excluding some of the packages in it ... I
> don't need sound, wireless, Bluetooth etc.
>
>
If you don't need sound, wifi, and bluetooth then remove the relevant flags
from DISTRO_FEATURES and they'll never be built.
WINDRES and RC values are exported when building for a mingw32 target. These
values, due to being exported, end up in the signature hash for everything in
the system. By adding these to the whitelist we prevent contamination and
allow the system to properly reuse existing -native and other sstate
Add the two specific exported values to the hash, otherwise task hashes change
and things rebuild unnecessarily. (perl-native may also fail to rebuild.)
Mark Hatle (1):
*-mingw32.conf: Add whitelist of WINDRES and RC to hash
conf/machine-sdk/i686-mingw32.conf | 2 ++
conf/machine-sdk/x86_64
Take a look at poky-tiny distro:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/distro/poky-tiny.conf
As you are using BBB you can optimize u-boot code and remove some board
detection steps.
I noticed that MLO generated by u-boot 2014.07 mainline is too much faster
than the o
Diego,
I agree with Ross here in from my experience with embedded systems the three
best ways to strip your root
file system are by removing unneeded boot loader coe, removing unneeded kernel
components and that of striping
your middle ware to smaller versions like Busybox and other similiar pack
11 matches
Mail list logo