Getting started with OE-Classic: Difference between revisions

From Openembedded.org
Jump to navigation Jump to search
Line 3: Line 3:
comment2
comment2


= Portability issues =
comment5
Make sure to set <nowiki>TARGET_OS</nowiki> to something other than linux in local.conf if your host isn't linux.
 
GNU extensions to tools are often required.  Symlink GNU patch, make, and cp (from fileutils), chmod, sed, find, tar, awk into your OE development path.
 
FreeBSD 4 users: Perl 5.0 is too old.  A more recent perl must be available as <nowiki>/usr/bin/perl</nowiki>.  Unfortunately just having more recent perl in the path isn't good enough.  Some scripts are hard-coded for <nowiki>/usr/bin/perl</nowiki>.  You can test for which perl you're using by typing perl -v.  see /usr/ports/UPDATING for instructions on updating perl. Don't forget to do a use.perl port as instructed in /usr/ports/UPDATING
 
FreeBSD users: Set <nowiki>BUILD_OS</nowiki> in local.conf to freebsdN where N is your major version number.  At least the cross gcc wants this.
 
FreeBSD users: The build process of glibc uses a very long command line at some places.  Increase ARG_MAX to at least 131072, by editing /usr/sys/sys/syslimits.h and recompile your kernel (and reboot).


= Productivity notes =
= Productivity notes =

Revision as of 06:36, 6 November 2009

comment4

comment2

comment5

Productivity notes

Use the interactive bitbake mode ("bitbake -i") to speed up work when debugging or developing .bb files. Remember to run "parse" at the prompt first. Go!

If you want to save some compile time or are interested in additional tweaks to local.conf take a look at the Advanced configuration page.

Retrieved from "https://www.openembedded.org/w/index.php?title=Getting_started_with_OE-Classic&oldid=1834"