**** BEGIN LOGGING AT Sun Feb 16 02:59:57 2020
Feb 16 10:30:02 <gaston64> hello, I am using yocto project to build a Linux image operating system for my embedded board. I need to install some elements to this image which are : g++, gdb, make, rsync, zip . How can I add them to my image please ?
Feb 16 10:35:24 <marex-cloud> gaston64: add them to  IMAGE_INSTALL
Feb 16 10:37:24 <gaston64> marex-cloud Okey thank you !
Feb 16 10:38:20 <gaston64> But can you tell me the difference between IMAGE_INSTALL , IMAGE_INSTALL_append , IMGAE_FEATURES , EXTRA_IMAGE_FEATURES ? please
Feb 16 10:38:55 <marex-cloud> gaston64: search for this _append only , there's wiki article about it
Feb 16 10:39:07 <marex-cloud> I'm on a phone, it's hard to type, sorry
Feb 16 10:40:34 <gaston64> marex-cloud Okey no problem, I am a little bit confused between them and when I want to add some features to my linux image I don't know where to put it in those variables
Feb 16 10:41:15 <marex-cloud> Into your image recipe or local.conf
Feb 16 10:41:52 <marex-cloud> When in doubt, git grep in meta or oe-core gives plenty of examples
Feb 16 10:43:09 <gaston64> marex-cloud Okey thanks
Feb 16 10:43:20 <marex-cloud> IMAGE_INSTALL is for adding packages, IMAGE_FEATURES is for well, features of the image, which is 'above' the recipes and recipes can be built differently depending on which features are enabled
Feb 16 10:45:48 <gaston64> when I want to add something to my image, I need to take a breath and choose if it is a feature or a package
Feb 16 10:46:19 <gaston64> It's hard to make a difference between them, isn't it ?
Feb 16 10:52:10 <marex-cloud> Recipes usually result in packages when they're built, but recipes may check for features to build packages in specific configuration
Feb 16 10:55:05 <gaston64> I see , this make it more clear for me thanks
Feb 16 11:00:03 <marex-cloud> It's also very simplified view
Feb 16 11:00:19 <marex-cloud> Cfr the mega manual for all the nuances
Feb 16 11:00:21 <yocti> New news from stackoverflow: Yocto Top Level Files <https://stackoverflow.com/questions/60247741/yocto-top-level-files>
Feb 16 11:02:15 <gaston64> Okey I will search for it
Feb 16 11:03:57 <gaston64> Now, I want to know how can I check if the desired packages are already existing into my image or I must add them manualy ? How can I see what packages are build into my image ?
Feb 16 11:04:49 <gaston64> I have .manifest file in /tmp/deploy/images/"my_board_name"
Feb 16 11:05:05 <gaston64> is this the right file to check ?
Feb 16 11:09:28 <marex-cloud> bitbake -e yourimage | grep IMAGE_INSTALL might be helpful, or check the image build dir
Feb 16 11:29:12 <gaston64> marex-cloud thank you for your support
Feb 16 11:30:25 <moustafa> hello
Feb 16 11:31:32 <moustafa> how I can deploy my qt app on yocto custom image ?
Feb 16 11:56:15 <marex-cloud> Write a recipe for it, add it to your IMAGE_INSTALL in image recipe
Feb 16 12:00:17 <moustafa> when I did it , it gave me=> do_unpack: Unpack failure for URL ............
Feb 16 15:36:22 <ferry_t> Hi I am building a initrd (not built-in initramfs). It is built into a hddimg together with bzImage and is working fine. However, my rootfs only has bzImage. I need to manually copy initrd there, then it boots. How do I add initrd there automatically?
Feb 16 16:01:13 <yocti> New news from stackoverflow: Yocto: overriding kernel configuration <https://stackoverflow.com/questions/60250078/yocto-overriding-kernel-configuration>
Feb 16 16:35:37 <ferry_t> @yocto I tried to answer the question on SO
Feb 16 16:36:03 <ferry_t> @yocti
Feb 16 21:02:06 <yocti> New news from stackoverflow: phytec phyBOARD iMX-6 performed poorly when running qt5 opengles application from flash instead of sd card (fps halved) <https://stackoverflow.com/questions/60252992/phytec-phyboard-imx-6-performed-poorly-when-running-qt5-opengles-application-fro>
**** ENDING LOGGING AT Mon Feb 17 02:59:57 2020