Difference between revisions of "Talk:Getting started with OE-Classic"

From Openembedded.org
Jump to: navigation, search
(Gulf Coast Western - 9722840600 / (972) 2840600 - Whos calling from - Due Diligence: new section)
m (moved Talk:Getting started to Talk:Getting started with OE-Classic: Move out of the way so that OE-Core info can be put in its place)
 
(9 intermediate revisions by 5 users not shown)
Line 18: Line 18:
 
git clone git://git.openembedded.net/bitbake
 
git clone git://git.openembedded.net/bitbake
 
</pre>
 
</pre>
 
== Todd Cowle & Ultimate Tier Advisors Ltd Announces Municipal Bond Info & Research ==
 
 
Todd Cowle Municipal Bond Credit Report synthesizes, analyzes and presents aggregate credit information and trends in the municipal bond market. The report includes municipal bond rating information from the three major rating agencies – Moody’s Investor Services, Standard and Poor’s and Fitch Ratings.
 
 
== Gulf Coast Western - 9722840600 / (972) 2840600 - Whos calling from - Due Diligence ==
 
 
Check this Out!
 
 
3 hrs ago I got a phone message from 9722840600 and was convinced the the person calling was a scam.
 
 
I decided to complain to the the company and yell.
 
 
I really screwed up... Gulf Coast Western -the oil company- was calling to approve my job application - apparently I got the job!
 
 
Any idea how to uncomplain and fix this?!!
 

Latest revision as of 14:55, 7 November 2012

Changing distro/machine

  • is it safe to change distro on the same oe tree? or mixed staged packages my produce unpredictible results?

It is not recommended as results can be disaster. Each distro can define other versions of each of libraries so in the end resulting packages are not what distro wants.

  • on angstrom build guide you can read that changing machine/libs is safe for *Angstrom*, is it safe for other distro too?

It is safe for any distro.

About The building time needed

  • I have several tries on building the very basic targets (bitbake nano/helloworld/task-base), every time it cannot complete in almost a whole night, on a Intel-3.2G-CPU/512M-Memory machine, so who can tell an approximate building time needed? On Day or one week? Thank you.

It depends on machine speed and amount of memory. On quad core Intel 2.4GHz with 4GB ram I am able to do console-image in 2-3 hours. But that can be also result of ccache being used with quite big storage used for caching. Build time can be longer for first build due to time required to fetch all sources so keep your DL_DIR outside of TMPDIR so next builds will use already fetched sources. You can also enable parallel make and use more BitBake threads to speed up build time (info how to do it ).

Bitbake GIT

  • The addition of the command to clone the bitbake tool will save time. The bitbake project homepage still list only the SVN repository. I have lost time to realize that bitbake repository is now in the openembedded site. Please add this somewere:
git clone git://git.openembedded.net/bitbake