From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6462206452988641280 X-Received: by 10.25.190.201 with SMTP id o192mr299477lff.22.1504602381410; Tue, 05 Sep 2017 02:06:21 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.138.196 with SMTP id m187ls1320989wmd.19.canary-gmail; Tue, 05 Sep 2017 02:06:21 -0700 (PDT) X-Google-Smtp-Source: ADKCNb6omaMv93T7vvDwX3PtoNTymNmV+5eObZDzohK+x7h8kVv2Ol2wARUitsxZb1B4dWLcKjph X-Received: by 10.28.46.67 with SMTP id u64mr311705wmu.7.1504602380991; Tue, 05 Sep 2017 02:06:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1504602380; cv=none; d=google.com; s=arc-20160816; b=VmtzyoCSM7pCIpOPWeymAvSp5hVFjVr7Jbx1a4We2dk+Et4YTZLSvjMh1FK2hfys1B U1f9l0eSekBck5iezqe+q1Cvs0AMFrErnPP+TgMjuJUXDy7pSXUgi/fgG6pZrkfsQgQY 8aCEIFTPgG4qhtX706jb4OZxtvKS7aweZTjT3kXdcPR3O0s137x6geQEvCZOpDLBTspe i1/xn+Ku1t8yoVO7BwArf8sjaUXu7deuUUmKpmwCXe7o+KREMzc9fE1Yq/xMLJGmpcrZ 0vYenNUm2nxzYx2oqZAjKtKSNrDHo7LknRs7YxCiCmwnCdrWYWfoQ8fBCz3rdTbg+9ub hGew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject :arc-authentication-results; bh=REvCQu3XPbsa/D+YgF5Paw/8ILdVwJG4oTGhIaiHmBk=; b=ZQRkTbMEd9IQs+YWY05U/5qIYck5bgaZS0nJ3Xyjoc97L0TCLllcauJWO0/m5FjJEX ML/+9xzUvNBGxbZUz90L2LOioeKI9Qqx5v3FnwW7u+BsLpFFYLfvrpkXHTqRVpV7JhK3 AyK1rgRC1y/1fodd7xdhoOIbMbwZUrgFrSe9SAyj7CNchyJNuKuCmbRJtqsyK/RXLm3S 0EoXZiYdjv7LoWU1Tb3q54YMnKPBdnS+2MGshuGpET95bwNYXPAvQBmjt/Mn2Zd0pCNA 17Ophyga1Pqb4noy/V1WdAEfgDVS7pO30N1HkRm1Nev6XWmBmfUqGl+SsKsLrdr6N0WS yCvA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 192.35.17.2 is neither permitted nor denied by best guess record for domain of claudius.heine.ext@siemens.com) smtp.mailfrom=claudius.heine.ext@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id 7si12158wme.7.2017.09.05.02.06.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Sep 2017 02:06:20 -0700 (PDT) Received-SPF: neutral (google.com: 192.35.17.2 is neither permitted nor denied by best guess record for domain of claudius.heine.ext@siemens.com) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 192.35.17.2 is neither permitted nor denied by best guess record for domain of claudius.heine.ext@siemens.com) smtp.mailfrom=claudius.heine.ext@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id v8596KaD014577 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 5 Sep 2017 11:06:20 +0200 Received: from [139.25.68.223] (linux-ses-ext02.ppmd.siemens.net [139.25.68.223]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id v8596JAl001959; Tue, 5 Sep 2017 11:06:20 +0200 Subject: Re: Isar build tree structure To: Alexander Smirnov , isar-users@googlegroups.com References: <7c829771-d78b-7409-ce86-74fae0f15dc4@ilbers.de> From: Claudius Heine Message-ID: <2b9b891a-055a-2e4f-60ba-dc87972769d9@siemens.com> Date: Tue, 5 Sep 2017 11:06:19 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <7c829771-d78b-7409-ce86-74fae0f15dc4@ilbers.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: nQNecXLql0YJ Hi, On 09/05/2017 10:21 AM, Alexander Smirnov wrote: > Hi all, > > I'd like to discuss build folders tree to somehow chose more suitable > approach. > > 1. How it's done at the moment. > > The folder tree contains the following main paths: > > - tmp/work/${PP} > > It's a $WORKDIR for each recipe, here is stored bibtbake logs and > commands, and data for packages that doesn't require buildchroot (for > example, buildchroot and isar-image-base). > > - tmp/work/buildchroot/${DISTRO}-${ARCH}/rootfs/home/build/${PN} > > This is the $BUILDROOT for packages, that require compilation in chroot. > It is used as destination folder for unpack task. > > Benefits: > > - Maximal common OE-like folder structure for all kind of recipes. You > can find the information about specific package in 'tmp/work/${PP}'. And > it doesn't matter if this package uses dpkg class, or not. > > - After buildchroot cleanup, the build information is not loosed. > > - For multiple buildchroots in project, there will be single place for > package meta information. > > 2. Remove $BUILDROOT. > > This would mean that $WORKDIR location may vary depending on recipe > type. So the recipes data will be distributed across buildchroots and > tmp/work dir. > > Benefits: > > - Each recipe will use single folder for everything. > > > > So... Ideas and opinions? :-) > Why not both benefits? Using bind mount to put the workdir of recipes into the buildchroot? Maybe we should take a look at proot [1] and use this instead of chroot, because its more flexible, does not require privileges, etc. [1] https://github.com/proot-me/PRoot/blob/master/doc/proot/manual.txt Claudius -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de