From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6491554293275951104 X-Received: by 10.80.230.25 with SMTP id y25mr388906edm.9.1513065776362; Tue, 12 Dec 2017 00:02:56 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.80.208.199 with SMTP id g7ls4394291edf.7.gmail; Tue, 12 Dec 2017 00:02:56 -0800 (PST) X-Google-Smtp-Source: ACJfBosARe8r5WY5tlQTclEa1aW9AaW++6LOQaoUkO3QqwdgtjXVc5QA9x6GJnJ0X2EOBY1R3+FJ X-Received: by 10.80.142.245 with SMTP id x50mr397944edx.0.1513065775936; Tue, 12 Dec 2017 00:02:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1513065775; cv=none; d=google.com; s=arc-20160816; b=MRnkS2a8IwI5VjuA8QWtQrie4mlSbt7JEA6+e74A+fywD4lYaSwWk8yaeEvStcs9Fj 4++58+7X9tMQ1ViosoV1xs8sZ3GuZCjJ38FrX692um1dRszIaoWNe4FR8hUqC7qSX6GC fGXfCievvvHTllq6bR747CqI+MB+fsO7FXxHZkcMQDxryJlnp/THZChUUHUeD6HsEjx3 PONHusuZFVzl04EGShbyfndvYufnxji/sa4j7LShpEem3zUmb3PZVasJdlurSlqHCpu3 WFg+ULyIhCsjPF9AYR6BCwKOf4E6QR0eY0pUWXqCyV6Rg2ylqV0OhLhr/eMgWDtKNZIq r7cA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:mail-followup-to:message-id :subject:to:from:date:arc-authentication-results; bh=3u09kvRaRwLr8ciyYygXYhb6llFuihwKoIci1MT3W4c=; b=MvV4PauTOg2hNw1yyGEzeXnYPmzBUjllDJsu2NxzXiMg3ylR3nrHKHe9pDCNNnTVRk MBeaz0CSOfvl4c3yW13vUFkTbfqMa2MjJWb/daKWYDaohSb/WrZmdxe2d04QVocq2hP6 UuOIAYJ83YQuM+75rR1V7Ef/euBsq/PTFBrBOrdWFCLPSQ79T5TKe7ofcxv9Xo63pxwx UPXNqMVsiG7mTKFpFiL/S3r9ncKinGKo/e/wwrF+Wfb5KALslmUk4yVUzeNXqQGG/ldr NSZUQUbv5INSXeJGkR+eQLiXIzZhq9O9WhYpWGfovqoJ9KfgxQGrILDAAJpG5Xqg/L7P 7jAQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of christian.storm@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=christian.storm@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id w21si2154366edl.5.2017.12.12.00.02.55 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Dec 2017 00:02:55 -0800 (PST) Received-SPF: pass (google.com: domain of christian.storm@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of christian.storm@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=christian.storm@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id vBC82tmE006152 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 12 Dec 2017 09:02:55 +0100 Received: from localhost ([139.25.69.251]) by mail3.siemens.de (8.15.2/8.15.2) with ESMTPS id vBC82t9t014581 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 12 Dec 2017 09:02:55 +0100 Date: Tue, 12 Dec 2017 09:01:04 +0100 From: Christian Storm To: isar-users@googlegroups.com Subject: Re: [PATCH 3/4 v2] buildchroot: Add prepare and cleanup tasks Message-ID: <20171212080104.ylkyqwovrdywnepy@MD1KR9XC.ww002.siemens.net> Mail-Followup-To: isar-users@googlegroups.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <16c190d8-c359-26cc-4933-93629b9a7b77@ilbers.de> User-Agent: Mutt/20170113 (1.7.2) X-TUID: p+CfyeUE6SlB > [...] > 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" Besten Gru�, Christian -- Dr. Christian Storm Siemens AG, Corporate Technology, CT RDA ITP SES-DE Otto-Hahn-Ring 6, 81739 M�nchen, Germany