Thank you Len.
If I specified PACKAGES = “${PN}” as mentioned early, it only built the main
package.
As you suggested, I removed that line from my c-mlib.bb, it then built the
main, -dev and -dbg packages as specified in the bitbake.conf - thanks you...
dinhn@rs-bldsrv:/media/raghuram/data/dinhn/ioxDevLatest/ioxsdk/yp$ find
tmp/deploy | grep c-mlib
tmp/deploy/ipk/core2-64/c-mlib-dbg_1.1-r0_core2-64.ipk
tmp/deploy/ipk/core2-64/c-mlib-dev_1.1-r0_core2-64.ipk
tmp/deploy/ipk/core2-64/c-mlib_1.1-r0_core2-64.ipk
tmp/deploy/licenses/c-mlib
But running into the other issue, which I replied to Paul’s email few minutes
ago. Please take a look if you have time. Thx
Thanks again Len.
—Dinh
On 10/4/16, 2:55 PM, "Lennart Sorensen" <lsore...@csclub.uwaterloo.ca> wrote:
>On Tue, Oct 04, 2016 at 07:47:58PM +0000, Dinh Nguyen (dinhn) wrote:
>>
>> Hi Paul, thanks much for prompt response.
>>
>> The c-mlib.bb below has the packages var as
>> PACKAGES =+ "${PN}” I also tried PACKAGES = "${PN}”
>
>Don't do that.
>
>In bitbake.conf you have:
>
>PACKAGES = "${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc ${PN}-locale
>${PACKAGE_BEFORE_PN} ${PN}"
>
>So all those package names are implied and always exist. Don't try to
>add them yourself.
>
>Only do anything with PACKAGES if you want to add any other package
>names or totally override the list of packages (in which case you have
>to use PACKAGES = of course)
>
>For example base-files does override the list completely, as does glibc
>and a few other ones, but most only add to it.
>
>--
>Len Sorensen
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
