From: Gyorgy Sarvari <skandigraun@gmail.com>
To: nguyenthaithuanalg@gmail.com, yocto@lists.yoctoproject.org
Subject: Re: [yocto] A new member
Date: Wed, 9 Apr 2025 16:40:22 +0200 [thread overview]
Message-ID: <7318f03d-649d-41d7-92d9-1e6596bb62b9@gmail.com> (raw)
In-Reply-To: <13400.1744206734783532039@lists.yoctoproject.org>
On 4/9/25 15:52, Thuận Nguyễn-Thái via Lists.Yoctoproject.Org wrote:
> Hi Gyorgy,
> It is wonderful, I see the output:
> "poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64-20250409111400.rootfs.ext4"
> in my PC.
> With commands below:
> git checkout dunfell
> source oe-init-build-env
> bitbake core-image-sato --runall=fetch ## get source
> bitbake core-image-sato ## Build source
> Now, I have a library, I want to integrate into yocto, and I hope the
> community take a look. On LinkedIn, Jan Flik - a director from Intel,
> told me refer to yocto/openBMC, and could contribute to the community.
> Can you give me some hints? I really appreciate if you do that.
To add your own software, you need to create a recipe, or a .bb file,
which describes how to compile and install your application.
You can find info on this topic here:
https://docs.yoctoproject.org/dev-manual/new-recipe.html
Especially check sections 5.1-5.3, which describe how to create new
recipes - the page is long, but these section are short, and easy to
read, it should give a good start.
Once you have the recipe, you need to add it to your image. It is also
fairly simple, described here:
https://docs.yoctoproject.org/dev-manual/customizing-images.html (this
page is pretty short).
There is one last thing I would like to note: I see from your commands
that you are using "dunfell" version.
If you can, you should use a different version - for example "scarthgap"
or "walnascar". Dunfell is old and unmaintained. It is not for new
projects - it is getting very outdated.
> My libary is "simplelog-topic":
> https://github.com/thuanalg/simplelog-topic
> Regards,
> Thuan Nguyen Thai
next prev parent reply other threads:[~2025-04-09 14:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 9:58 A new member Thuận Nguyễn-Thái
2025-04-09 11:08 ` [yocto] " Gyorgy Sarvari
2025-04-09 13:52 ` Thuận Nguyễn-Thái
2025-04-09 14:40 ` Gyorgy Sarvari [this message]
2025-04-09 17:06 ` Thuận Nguyễn-Thái
2025-04-09 17:20 ` Gyorgy Sarvari
2025-04-11 10:52 ` Thuận Nguyễn-Thái
2025-04-11 11:48 ` Gyorgy Sarvari
2025-04-11 12:08 ` Thuận Nguyễn-Thái
2025-04-11 12:15 ` Alexander Kanavin
2025-04-11 12:18 ` Thuận Nguyễn-Thái
2025-04-11 12:46 ` Alexander Kanavin
2025-04-12 3:28 ` Thuận Nguyễn-Thái
2025-04-12 6:57 ` Gyorgy Sarvari
2025-04-12 7:31 ` Thuận Nguyễn-Thái
2025-04-12 16:08 ` Thuận Nguyễn-Thái
2025-04-12 16:58 ` Gyorgy Sarvari
2025-04-12 17:49 ` Thuận Nguyễn-Thái
2025-05-03 16:37 ` Thuận Nguyễn-Thái
2025-05-03 17:35 ` Gyorgy Sarvari
2025-04-12 16:09 ` Thuận Nguyễn-Thái
2025-04-11 12:16 ` Quentin Schulz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7318f03d-649d-41d7-92d9-1e6596bb62b9@gmail.com \
--to=skandigraun@gmail.com \
--cc=nguyenthaithuanalg@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox