From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Qi.Chen@windriver.com>
Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id DB064E01440
	for <yocto@yoctoproject.org>; Mon,  2 Sep 2013 19:05:28 -0700 (PDT)
Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com
	[147.11.189.40])
	by mail1.windriver.com (8.14.5/8.14.3) with ESMTP id r8325TAp013711
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL)
	for <yocto@yoctoproject.org>; Mon, 2 Sep 2013 19:05:29 -0700 (PDT)
Received: from [128.224.162.233] (128.224.162.233) by ALA-HCA.corp.ad.wrs.com
	(147.11.189.50) with Microsoft SMTP Server (TLS) id 14.2.347.0;
	Mon, 2 Sep 2013 19:05:27 -0700
Message-ID: <52254404.4040602@windriver.com>
Date: Tue, 3 Sep 2013 10:05:56 +0800
From: ChenQi <Qi.Chen@windriver.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: <yocto@yoctoproject.org>
References: <CAFyqS9o02b7W4LBhuPkRzo09yR74g71gEWyEvVJ5Ug-0XMD3yQ@mail.gmail.com>
In-Reply-To: <CAFyqS9o02b7W4LBhuPkRzo09yR74g71gEWyEvVJ5Ug-0XMD3yQ@mail.gmail.com>
X-Originating-IP: [128.224.162.233]
Subject: Re: header file missing in populated SDK
X-BeenThere: yocto@yoctoproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Discussion of all things Yocto Project <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2013 02:05:33 -0000
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit

On 09/02/2013 10:56 PM, Hans Beckérus wrote:
> Hi. We are having some issues figuring out why one of our header files
> fails to be installed properly into the SDK. The header file is
> currently installed using a few lines in one of our recipe:
>
> do_install_append() {
>          install -m 0644 ${S}/foo.h
> ${STAGING_DIR}/${MACHINE}${includedir}/linux/foo.h
> }
Please don't do that.
I think just installing the foo.h into the ${D}${includedir} would do. 
And foo.h will end up in the FOO-dev package.
Make sure that the FOO package is in the IMAGE_INSTALL list, and then 
use 'bitbake <your-image-recipe> -cpopulate_sdk' command to populate the 
SDK.

> foo.h ends up ok in our build/tmp/sysroots,
sysroots != SDK
The files under build/tmp/sysroots are usually generated by the 
do_populate_sysroot task of each recipe.

 From my understanding, SDK is composed of two parts, the target part 
and the nativesdk part.
The nativesdk part is determined by the TOOLCHAIN_HOST_TASK.
And the target part is determined by the TOOLCHAIN_TARGET_TASK.
The reason that we could only ensure that FOO is in IMAGE_INSTALL is 
because in image.bbclass, we have:
TOOLCHAIN_TARGET_TASK += "${PACKAGE_INSTALL}"
export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${ROOTFS_BOOTSTRAP_INSTALL} 
${FEATURE_INSTALL}"

The process of populating SDK is also composed of two parts, installing 
the target packages and installing the nativesdk packages. See 
populate_sdk_xxx.bbclass for more details.

Best Regards,
Chen Qi

>   but it does not make it to the SDK.
> Is our do_install_append wrong in some way, does it have to be updated
> to support SDK builds? Maybe it is wrong to use ${MACHINE} here?
>
> Thanks.
> Hans
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>