From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6491554293275951104 X-Received: by 10.223.168.76 with SMTP id l70mr371065wrc.29.1513066912066; Tue, 12 Dec 2017 00:21:52 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.5.147 with SMTP id 141ls2031642wmf.4.gmail; Tue, 12 Dec 2017 00:21:51 -0800 (PST) X-Google-Smtp-Source: ACJfBovO/zJKRay3EQR8j8wwJ9EGzfUzLJvJtmw+/59FGQ+Yr4xT38yfM+iT5PjAjMbGBQFbeN5j X-Received: by 10.28.126.197 with SMTP id z188mr92693wmc.14.1513066911683; Tue, 12 Dec 2017 00:21:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1513066911; cv=none; d=google.com; s=arc-20160816; b=hmMdX06BLsDmmLW2Wr1gVDBjc62jctSbv1podzPygg/SMwftgn/Syez029/0s8zEHq 41zQ8Vdpj2c46C3kI3Fy4PnhPR0KoQiC3AIFXWol4YmPINYMYnKHGIewtiTHdIJvgw9D FfeK5DMNsdKaUBsNznokUcoVQc9SJ/132GD7Bu1aqKOS0V92CWJ9Tp2TUsSwTWH2YJNW Y7LhwCi322fVzBZ+vqabzhzzUshMrO90UHZiU0kkrIWyLzy0McMU0049rlUIsUlyUhD6 XEZ42hdRevCLRutC4Jz5vqWqwbJeDbR1Uq8nfm/b7T4tgSIgfqZzX5ozxhuSsnlF84FV H0jA== 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=JsqoSdrFAo3W8Qk8sCsdglfpcMWGmmBMNA6ipjWZ23o=; b=Ls/MpM1dJ4nbvuxG/0lVbrVdUBGrs9C+Ti9ruzYHpNyeMDPsrSYUiGZ+aLZkE+wfky 3VkzxrJY0YUrWRIr0UyFLBJ1vSdA2o4eSWd3p70PvzXNlURxGovJ59w6+QFLoQfQNRbi V4zCPAKZsUVERhG3RkByMCmUpjpKm/69NKv85OuIx+KA2FhGx4HbvTwOnr8AeAhssvl0 I/KC7a09Zhhzn2aWpEUari9TlBnfrCkWUcaeIICW+OihudzoYL7yFteBmRu/t6GfYzoi yMkF7D/YrRayAC0qFWKvVO0ro0ezQ+3IfZ+/wICHgKw1mTrHc7zBQ5EleczpzXup4s8U +P7g== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id j2si1418040wrh.0.2017.12.12.00.21.51 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Dec 2017 00:21:51 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Received: from [10.0.2.15] (client.yota.ru [188.162.65.100] (may be forged)) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id vBC8LlRF027253 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Tue, 12 Dec 2017 09:21:50 +0100 Subject: Re: [PATCH 3/4 v2] buildchroot: Add prepare and cleanup tasks To: isar-users@googlegroups.com References: <20171212080104.ylkyqwovrdywnepy@MD1KR9XC.ww002.siemens.net> From: Alexander Smirnov Message-ID: <1e453b72-694b-49f1-1c99-2f183eba7140@ilbers.de> Date: Tue, 12 Dec 2017 11:21:42 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20171212080104.ylkyqwovrdywnepy@MD1KR9XC.ww002.siemens.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: uPT1T55m29GH On 12/12/2017 11:01 AM, Christian Storm wrote: >> [...] >> BTW: why can't you add this hack to 'build.sh', after >> 'dpkg-buildpackage' complete, just run 'dpkg -i' on newly baked >> packages. Also ugly, but no headache with deps parsing. :-) > > Yes, could do that, for the time being. But this installs each and every > package into the buildchroot, I just need one. However, I think I go for > this to not loose contact to -next's HEAD. > >>> sudo chroot ${BUILDCHROOT_DIR} /build.sh ${PP}/${SRC_DIR} >>> ... >>> } >>> ``` >>> >>> This does not work on current -next. Even if you do the >>> do_build[deptask] = "do_build" >>> because do_cleanup() kicks in and unmounts ${BUILDCHROOT_DIR}/git >>> and the task reordering of deploy_deb(). >>> >>> >>> Hope this example helps? >> >> Probably I get the possible issue. How do you add packages A and B to >> the build chain, via IMAGE_INSTALL? If so, where do you set >> IMAGE_INSTALL variable? > > I do have a meta-mylayer/recipes-core/images/image-mybox.bb in which I > do IMAGE_INSTALL_append = " B" > I think that's the problem with current series. I assume that IMAGE_INSTALL is global variable, like in pure Isar where it's set in 'local.conf' file. If you append IMAGE_INSTALL locally in recipe, this changes won't be seen in buildchroot recipe, so DEPENDS += "${IMAGE_INSTALL}" makes no sense. Ok, will drop it. Alex