From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6462206452988641280 X-Received: by 10.28.207.5 with SMTP id f5mr351356wmg.32.1504603719695; Tue, 05 Sep 2017 02:28:39 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.25.199.17 with SMTP id x17ls60670lff.44.gmail; Tue, 05 Sep 2017 02:28:39 -0700 (PDT) X-Google-Smtp-Source: ADKCNb6o1LRg8QmxOIN4Hf0Yg5JS/mBNgRTlAyn1w65Tcr0bfpWN0X/55phyz3D+JZZj6ehIYWNM X-Received: by 10.46.31.2 with SMTP id f2mr351906ljf.31.1504603719368; Tue, 05 Sep 2017 02:28:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1504603719; cv=none; d=google.com; s=arc-20160816; b=JplC8oK/3EJefjK8rdzCWyXOo7Muv2sbg0OmN2zg3wv2WnCKm1SSJg2gsgP1/p7bKM Ghl2rMy4wfzvWVwC0tpswRvzTbHvg+STU4ezs7ROSJlH+XVzA449iuBmEuidW2p1Adj8 K8J6BWM7yPfiQa6cQqaHF9QhVl8wAN/GrWhUc+R39HsPmAA4n4pKzKMgizkSTvuks/71 02wQ30dKPD/A16BcDRH4eAVJaOKsODcSejsNIrfNCf3RN6cDcRNgFL4Ityj8xKeo48xf R2wYinJ8frYR+O6Z9+jla332ovoaIas1/dmfAX5NuSyOq8L9uDdsB123uPfVVMEO+GWr o9yQ== 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:cc:to:subject :arc-authentication-results; bh=xTPjyC30oikDY9UopEThctx3c+RKSbzuy9QdPZGjX6A=; b=cIu6RbJIooEe9Xkj/Fp7o4pWVzKa/XyeVxi1ekIs+n0sh/ecfOaTHdcXqE17RjnrvW VkWLqf+aNlxtxyV8JllgH+TCCeI1O189VHhq93Cdt3KzH1Bo2lM4iNYcoMjjxgNlxSmT tLNTH/lFN3/tNMcAoGZEVvb5kwuWj2Vr9PH7aTa5ShGHqM67BB2zYANfqH9W4qHaOuig xGOijNWht95w2m8FVXM+V8TEcvf23PPIhfZNLKeiOiETk2etgeK42S4exjT1r3+addBc UpY/cPZXqfTKqtSRntR/DJ66dmx5NGf5DDTpPa0CcA+GVNnInwLvM3KDdfKPceup+HBK FE8A== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 192.35.17.28 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 goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id 74si4148wmf.8.2017.09.05.02.28.39 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Sep 2017 02:28:39 -0700 (PDT) Received-SPF: neutral (google.com: 192.35.17.28 is neither permitted nor denied by best guess record for domain of claudius.heine.ext@siemens.com) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 192.35.17.28 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 goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id v859Sc8q017101 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 5 Sep 2017 11:28:38 +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 v859Scgm001414; Tue, 5 Sep 2017 11:28:38 +0200 Subject: Re: Isar build tree structure To: Alexander Smirnov Cc: isar-users@googlegroups.com References: <7c829771-d78b-7409-ce86-74fae0f15dc4@ilbers.de> <2b9b891a-055a-2e4f-60ba-dc87972769d9@siemens.com> <44061e32-aa48-b432-ead5-5d6627b707b4@ilbers.de> From: Claudius Heine Message-ID: Date: Tue, 5 Sep 2017 11:28:38 +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: <44061e32-aa48-b432-ead5-5d6627b707b4@ilbers.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: AaCnvChjkkoZ On 09/05/2017 11:13 AM, Alexander Smirnov wrote: > > > On 09/05/2017 12:06 PM, Claudius Heine wrote: >> 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? > > Mount is very difficult to manage. For example if something failed > during build, it's hard to check in next build what is already mounted > and what is not yet. > > But your idea is good. Could we use symlinks instead? If you are in a chroot environment the paths of the symlinks are wrong since they reference a different root directory. > >> >> 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 >> > > Do you know if it fully supports dpkg & Co? I currently use proot in some parts of my isar fork already. And from my experience it works rather well. Since it uses the ptrace systemcall, static binaries work work as well. 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