From patchwork Thu Sep 19 10:59:54 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: kim.hansen@prevas.dk X-Patchwork-Id: 275942 X-Patchwork-Delegate: esben@haabendal.dk Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from hugin.dotsrc.org (hugin.dotsrc.org [IPv6:2001:878:346::102]) by ozlabs.org (Postfix) with ESMTP id 3F3942C0119 for ; Thu, 19 Sep 2013 21:01:10 +1000 (EST) Received: from hugin.dotsrc.org (localhost [127.0.0.1]) by hugin.dotsrc.org (Postfix) with ESMTP id E0624447B1 for ; Thu, 19 Sep 2013 13:01:08 +0200 (CEST) X-Original-To: dev@oe-lite.org Delivered-To: dev@oe-lite.org Received: from mail02.prevas.se (mail02.prevas.se [62.95.78.10]) by hugin.dotsrc.org (Postfix) with ESMTPS id 14D36447B1 for ; Thu, 19 Sep 2013 13:01:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=prevas.dk; i=@prevas.dk; l=2594; q=dns/txt; s=ironport2; t=1379588464; x=1411124464; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=8/5G7Jxo3zV5abao2yk+YXfjfWZJu8SiYRtDu7QA3mo=; b=XxxZJrCGOCSBNPSzv8axSwjeTOEmPU4zJUoX1YqDuE4J+gvWb6pz/zgM vEJout3cEKqM1z/U7tCVCfuAOyAwDl+Sa1QI/3XhPKGYQ/rrWaC77lmKP 2URfCNzvlqywlr4lXWEjj8wQ7zXxukNJgn3bb/8MF9qdc7wiRZXIKbWzd U=; X-IronPort-AV: E=Sophos;i="4.90,936,1371074400"; d="scan'208";a="3606476" Received: from vmprevas3.prevas.se (HELO smtp.prevas.se) ([172.16.8.103]) by ironport2.prevas.se with ESMTP/TLS/AES128-SHA; 19 Sep 2013 13:01:03 +0200 Received: from arh146.prevas.dk (172.16.11.14) by smtp.prevas.se (172.16.8.105) with Microsoft SMTP Server (TLS) id 14.2.347.0; Thu, 19 Sep 2013 13:01:03 +0200 Received: by arh146.prevas.dk (Postfix, from userid 1000) id 9740F2741530; Thu, 19 Sep 2013 13:00:10 +0200 (CEST) From: To: Subject: [doc 3/3] add first steps to build chapter Date: Thu, 19 Sep 2013 12:59:54 +0200 Message-ID: <1379588394-28990-3-git-send-email-kim.hansen@prevas.dk> X-Mailer: git-send-email 1.8.4 In-Reply-To: <1379588394-28990-1-git-send-email-kim.hansen@prevas.dk> References: <1379588394-28990-1-git-send-email-kim.hansen@prevas.dk> MIME-Version: 1.0 X-Originating-IP: [172.16.11.14] X-BeenThere: dev@oe-lite.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: OE-lite development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dev-bounces@oe-lite.org Errors-To: dev-bounces@oe-lite.org From: Kim Højgaard-Hansen --- build.txt | 52 +++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 51 insertions(+), 1 deletion(-) diff --git a/build.txt b/build.txt index 5f5630a..ebd335e 100644 --- a/build.txt +++ b/build.txt @@ -13,4 +13,54 @@ an SDK toolchain image, and so on. Building is done with the OE-lite Bakery sub-command called "bake". -TBD... +Before building you need to setup the build configuration in the file ++conf/local.conf+. + +A very minimal example configuration purely to test that building works: + +-------- +DISTRO = "base" +MACHINE_CPU = "arm-926ejs" +PROVIDED = "all" +SDK_CPU = "i686" +SDK_OS = "linux-gnu" +RMWORK = "0" +-------- + +The +DISTRO+ variable selects the OE-lite +xref:_oe_lite_terminology[distribution]. Here we choose a simple distribution +called base to be able to build something. Next we set the cpu we want to +cross compile for using +MACHINE_CPU+. It is also possible to set +MACHINE+ to +target a specific board e.g. raspberry-pi or pandaboard. +The +PROVIDED+ variable is used to inform the bake command what dependencies +can be assumed to be provided on the host system. See +conf/provided/all.conf+ +in the core metadata layer. The +SDK+ variables are used to specify what +architecture the OE-lite xref:_oe_lite_terminology[SDK] should be build for. ++RMWORK+ currently need to be set to 0 since automatic removal of temporary +build files is not implemented. Optionally you may want to set ++PARALLEL_MAKE = "-j X"+ where X is the number of CPUs available on your host +system + 1, to speed up the build. + +Now it is possible to choose something to build with the bake command. In +OE-lite all xref:_oe_lite_terminology[recipes] can be build. A recipe is a +file with the +.oe+ file extension, take a look at what recipes you have in +your current manifest using: + +-------- +find . -name '*.oe' +-------- + +The primary goal of the building process in OE-lite is to produce deployable +images, so for this example we will build an image. In the base metadata layer +a rootfs image recipe is located in: +recipes/images+ which we can try +building: + +-------- +oe bake base-rootfs +-------- + ++oe+ will resolve the list of dependencies, present you with a list of what +needs to be built and ask for confirmation before continuing. The build +process takes a while, but in the end you should see that base-rootfs was +build and the elapsed build time. The deployable images are now located in ++tmp/images+