A new member

A new member

[Thuận Nguyễn-Thái]

[-- Attachment #1: Type: text/plain, Size: 174 bytes --]

Hi all,
I am a new one, I am using CentOS 9, I have questions:
1. Can I build yocto in CentOS 9?
2. If yes, may you give me some hints?
Best regards,
Thuan Nguyen Thai

[-- Attachment #2: Type: text/html, Size: 240 bytes --]

Re: [yocto] A new member

[Gyorgy Sarvari]

On 4/9/25 11:58, Thuận Nguyễn-Thái via lists.yoctoproject.org wrote:
> Hi all,
> I am a new one, I am using CentOS 9, I have questions:
> 1. Can I build yocto in CentOS 9?

You can always check the supported systems here:
https://docs.yoctoproject.org/dev/ref-manual/system-requirements.html -
make sure to select the correct Yocto version at the top.

CentOS Stream 9 is supported and tested, for the latest Yocto release
(Walnascar and master branch). It *may* work for older versions too, but
it's not tested - it is not recommended however to use untested systems.
Strange and cryptic errors can pop up otherwise.
> 2. If yes, may you give me some hints?
Feel free to ask if you face any specific problems or have any questions
- that's why this mailing list exists.
> Best regards,
> Thuan Nguyen Thai
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#65129): https://lists.yoctoproject.org/g/yocto/message/65129
> Mute This Topic: https://lists.yoctoproject.org/mt/112169356/6084445
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [skandigraun@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Re: [yocto] A new member

[Thuận Nguyễn-Thái]

[-- Attachment #1: Type: text/plain, Size: 705 bytes --]

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.
My libary is "simplelog-topic": https://github.com/thuanalg/simplelog-topic
Regards,
Thuan Nguyen Thai

[-- Attachment #2: Type: text/html, Size: 901 bytes --]

Re: [yocto] A new member

[Gyorgy Sarvari]

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

Re: [yocto] A new member

[Thuận Nguyễn-Thái]

[-- Attachment #1: Type: text/plain, Size: 129 bytes --]

Hi Gyorgy,
I don't see "recipetool, bitbake-layers", please tell me how to find it out?
Thank you so much.
Thuan Nguyen Thai

[-- Attachment #2: Type: text/html, Size: 188 bytes --]

Re: [yocto] A new member

[Gyorgy Sarvari]

On 4/9/25 19:06, Thuận Nguyễn-Thái via Lists.Yoctoproject.Org wrote:
> Hi Gyorgy,
> I don't see "recipetool, bitbake-layers", please tell me how to find
> it out?

Both "recipetool" and "bitbake-layers" are Python scripts, part of the
base Yocto that you have already cloned.

You just need to run "source oe-init-build-env" (just like most probably
you did before generating your first image).

After that these commands will be added to your $PATH, and you can just
type "recipetool" or "bitbake-layers" into your terminal directly to use
them.

> Thank you so much.
> Thuan Nguyen Thai

Re: [yocto] A new member

[Thuận Nguyễn-Thái]

[-- Attachment #1: Type: text/plain, Size: 254 bytes --]

Hi Gyorgy,
Thank you so much, I can add/build successfully a recipy in Yocto.
I have a question, I have a project and wan to contribute what should I do?  Firstly, is there someone review my project check quality, feature, ...?
Best regards,
Thuan

[-- Attachment #2: Type: text/html, Size: 319 bytes --]

Re: [yocto] A new member

[Gyorgy Sarvari]

On 4/11/25 12:52, Thuận Nguyễn-Thái via Lists.Yoctoproject.Org wrote:
> Hi Gyorgy,
> Thank you so much, I can add/build successfully a recipy in Yocto.
> I have a question, I have a project and wan to contribute what should
> I do?  Firstly, is there someone review my project check quality,
> feature, ...?
If you have an project that would be useful for others too, and you
would like to contribute for the Yocto community, that would be fantastic!

Most new recipes can be submitted to the meta-openembedded layer, which
accepts contributions via mailing list, and also via GitHub pull requests.
You can find info on this in the readme of this layer:
https://github.com/openembedded/meta-openembedded/tree/master/meta-oe

Once you submit your recipe, it will go through 2 main processes:
1. Peer review - people look at your patch, and if they find anything to
change, they will tell you.
2. Your recipe will be also compiled for a number of platforms, to
ensure that the recipe is correct. If it fails, you will be informed
about it.

Generally submitting your patch via the mailing list is preferred, this
is where more people will see it. GitHub works too, but there are much
less feedback there.

Hope this helps.

> Best regards,
> Thuan

Re: [yocto] A new member

[Thuận Nguyễn-Thái]

[-- Attachment #1: Type: text/plain, Size: 332 bytes --]

Hi Gyorgy,
Let me paraphrase your hints by the steps below:
1. I fork a new one from "master" as: https://github.com/thuanalg/poky
2. Add my new recipe into "meta-openembedded"
3. Send mail to the Admin about my recipe. If that which email? Khem Raj raj.khem@gmail.com? ( raj.khem@gmail.com )
Best regards,
Thuan Nguyen Thai

[-- Attachment #2: Type: text/html, Size: 1729 bytes --]

Re: [yocto] A new member

[Alexander Kanavin]

On Fri, 11 Apr 2025 at 14:08, Thuận Nguyễn-Thái via
lists.yoctoproject.org
<nguyenthaithuanalg=gmail.com@lists.yoctoproject.org> wrote:
> Let me paraphrase your hints by the steps below:
> 1. I fork a new one from "master" as: https://github.com/thuanalg/poky
> 2. Add my new recipe into "meta-openembedded"
> 3. Send mail to the Admin about my recipe. If that which email? Khem Raj raj.khem@gmail.com?

Hello,

I would suggest something different. First, create your own layer,
e.g. meta-myproject, and add your recipe to it. Then you can publish
this layer (with the recipe) on github, without having to ask anyone.
And only then we can consider if the recipes in it can be moved to one
of the official layers.

Alex

Re: [yocto] A new member

[Thuận Nguyễn-Thái]

[-- Attachment #1: Type: text/plain, Size: 231 bytes --]

Hi Alex,
In order to be simple because I am new member, may I send mail to Khem Raj or share my project: https://github.com/thuanalg/simplelog-topic , is it good enough to contribute?
Is it OK?
Best regards,
Thuan Nguyen Thai

[-- Attachment #2: Type: text/html, Size: 3134 bytes --]

Re: [yocto] A new member

[Alexander Kanavin]

On Fri, 11 Apr 2025 at 14:18, Thuận Nguyễn-Thái via
Lists.Yoctoproject.Org
<nguyenthaithuanalg=gmail.com@lists.yoctoproject.org> wrote:
> In order to be simple because I am new member, may I send mail to Khem Raj or share my project: https://github.com/thuanalg/simplelog-topic, is it good enough to contribute?

Sending email to people about your own projects is usually not a good
idea. If you have questions, ask them here. But first please describe
your goal clearly, because I do not understand what do you want to
achieve.

Alex

Re: [yocto] A new member

[Thuận Nguyễn-Thái]

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

Thank  Alex, Gyorgy,
Now I added a recipe: https://github.com/thuanalg/meta-openembedded/tree/scarthgap/meta-oe/recipes-libsimplelog/libsimplelog , and verify of building on my local PC.
What should I do next? So sorry if it disturbs you, but I am new one the many thing is strange/new with me.
Best regards,
Thuan Nguyen Thai

[-- Attachment #2: Type: text/html, Size: 539 bytes --]

Re: [yocto] A new member

[Gyorgy Sarvari]

It is not a good idea to hijack other, unrelated discussions - please
keep the issues in their own threads.

This is a voluntary mailing list, definitely not real time and people
are answering request in their free time, and having to wait a day or
even more is expected, especially at weekends.

Quentin has sent you a link with useful info about contributing, please
go through it. It is mentioned in it that new contributions should be
based on the master branch (not Scarthgap, nor other branches. Releases
are for end-users, master branch is for development). Release branches
don't accept new recipes, only bug- and security fixes.

In the readme of the layer it is also explained how it accepts
contributions: preferably send a mail with your patch to the relevant
mailing list with git send-email (even the command is mentioned there),
or open a Github Pull Request.

On 4/12/25 05:28, Thuận Nguyễn-Thái via lists.yoctoproject.org wrote:
> Thank  Alex, Gyorgy,
> Now I added a recipe:
> https://github.com/thuanalg/meta-openembedded/tree/scarthgap/meta-oe/recipes-libsimplelog/libsimplelog,
> and verify of building on my local PC.
> What should I do next? So sorry if it disturbs you, but I am new one
> the many thing is strange/new with me.
> Best regards,
> Thuan Nguyen Thai
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#65146): https://lists.yoctoproject.org/g/yocto/message/65146
> Mute This Topic: https://lists.yoctoproject.org/mt/112169356/6084445
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [skandigraun@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Re: [yocto] A new member

[Thuận Nguyễn-Thái]

[-- Attachment #1: Type: text/plain, Size: 78 bytes --]

Hi Gyorgy,
It is my bad. Thank for your reminder of the rule.
Thuan Nguyen

[-- Attachment #2: Type: text/html, Size: 111 bytes --]

Re: [yocto] A new member

[Thuận Nguyễn-Thái]

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]

Hi Gyorgy,
From "Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'" ( https://github.com/openembedded/meta-openembedded/tree/master/meta-oe) , but I could not create/push a branch into " https://github.com/openembedded ( https://github.com/openembedded/meta-openembedded/tree/master/meta-oe) ) ". Therefore, I created "https://github.com/thuanalg/simplelog-topic/tree/main/meta-libsimplelog", and want to send it to " openembedded-devel@lists.openembedded.org ". How do you think?
Best regards,
Thuan Nguyen Thai

[-- Attachment #2: Type: text/html, Size: 885 bytes --]

Re: [yocto] A new member

[Gyorgy Sarvari]

I am not in the position to say what contribution to/not to accept in
the project, but I have seen accepted deviations from the contribution
guidelines very rarely, and making such the first contribution is not
the best. It is a fairly extensive project, without adhering to the
contribution rules the maintainers would just drown.

Unfortunately I am not able to give a tutorial about using git
send-email or the mechanics of opening a GitHub pull request on this
list. These are not Yocto/OpenEmbedded specific tools, but widely used
ones - this however also means that there is ample information about
them on the internet. It is definitely worth to master at least the
basics of GitHub, how community sw development works there - not only
for this project. And git send-email looks only complicated until one
configures it using the first result from stackoverflow.

I think maybe your journey with Yocto should start at a bit different
point, rather than contributing code changes. Familiarize yourself with
the project, how it works, what it offers, what you can do with it -
Yocto has a fairly steep learning curve, but start using it small, and
keep experimenting with new areas. Start with tutorials, and of course
the documentation, of which the project has plenty. It is easier to see
through what's going on and what helps the project when you are a real user.

On 4/12/25 18:08, Thuận Nguyễn-Thái via lists.yoctoproject.org wrote:
> Hi Gyorgy,
> From "Send pull requests to openembedded-devel@lists.openembedded.org
> with '[meta-oe]' in the subject'"
> (https://github.com/openembedded/meta-openembedded/tree/master/meta-oe),
> but I could not create/push a branch into
> "https://github.com/openembedded
> <https://github.com/openembedded/meta-openembedded/tree/master/meta-oe)>".
> Therefore, I created
> "https://github.com/thuanalg/simplelog-topic/tree/main/meta-libsimplelog",
> and want to send it to "openembedded-devel@lists.openembedded.org".
> How do you think?
> Best regards,
> Thuan Nguyen Thai
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#65153): https://lists.yoctoproject.org/g/yocto/message/65153
> Mute This Topic: https://lists.yoctoproject.org/mt/112169356/6084445
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [skandigraun@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Re: [yocto] A new member

[Thuận Nguyễn-Thái]

[-- Attachment #1: Type: text/plain, Size: 94 bytes --]

Hi Gyorgy,
Thank you so much.
So sorry if I did disturb.
Best regards,
Thuan Nguyen Thai

[-- Attachment #2: Type: text/html, Size: 149 bytes --]

Re: [yocto] A new member

[Thuận Nguyễn-Thái]

[-- Attachment #1.1: Type: text/plain, Size: 378 bytes --]

Hi Gyorgy,

I did build and test on my environment, it is OK.
I did " *git send-email -M -1 --to openembedded-devel@lists. openembedded.org ( openembedded-devel@lists.openembedded.org ) --subject-prefix="meta-oe][ PATCH"* ", my repo is: https://github.com/thuanalg/meta-openembedded/tree/libsimplelog ,
Does it match with Khem's guidance?
Best regarsd,
Thuan Nguyen Thai

[-- Attachment #1.2: Type: text/html, Size: 708 bytes --]

[-- Attachment #2: Screenshot from 2025-05-03 17-03-25.png --]
[-- Type: image/png, Size: 69184 bytes --]

Re: [yocto] A new member

[Gyorgy Sarvari]

On 5/3/25 18:37, Thuận Nguyễn-Thái via Lists.Yoctoproject.Org wrote:
> Hi Gyorgy,
> I did build and test on my environment, it is OK.
> I did "*git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix="meta-oe][PATCH"*", my repo is:
> https://github.com/thuanalg/meta-openembedded/tree/libsimplelog,
> Does it match with Khem's guidance?

You have added a new recipe, but haven't removed the one that's
currently present - so with the latest patch there would be 2
libsimplelog recipes. You need to use "git mv" command, or "git rm" +
"git add" to perform the move to the new folder, instead of duplication.

> Best regarsd,
> Thuan Nguyen Thai

Re: [yocto] A new member

[Thuận Nguyễn-Thái]

[-- Attachment #1: Type: text/plain, Size: 526 bytes --]

Hi Gyorgy,
From "Send pull requests to openembedded-devel@... with '[meta-oe]' in the subject'" ( https://github.com/openembedded/meta-openembedded/tree/master/meta-oe) , but I could not create/push a branch into " https://github.com/openembedded ( https://github.com/openembedded/meta-openembedded/tree/master/meta-oe) ) ". Therefore, I created "https://github.com/thuanalg/simplelog-topic/tree/main/meta-libsimplelog", and want to send it to " openembedded-devel@... ". How do you think?
Best regards,
Thuan Nguyen Thai

[-- Attachment #2: Type: text/html, Size: 4302 bytes --]

Re: [yocto] A new member

[Quentin Schulz]

Hi,

On 4/11/25 2:08 PM, Thuận Nguyễn-Thái via lists.yoctoproject.org wrote:
> You don't often get email from nguyenthaithuanalg=gmail.com@lists.yoctoproject.org. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
> Hi Gyorgy,
> Let me paraphrase your hints by the steps below:
> 1. I fork a new one from "master" as: https://github.com/thuanalg/poky

No, as

https://github.com/thuanalg/meta-openembedded

poky is not meta-openembedded, don't mix both.

Similarly, poky is not openembedded-core (often shortened to OE-Core).

> 2. Add my new recipe into "meta-openembedded"

So far so good. It'll need to be in one of the "sub"layers, whatever is 
the most appropriate for your recipe. Cannot tell you what that would be.

You could also have your own layer in your own git repository as 
Alexander just suggested in another mail.

> 3. Send mail to the Admin about my recipe. If that which email? Khem Raj raj.khem@gmail.com?<mailto:raj.khem@gmail.com>

Then you follow the instructions from the README inside the layer.

The same set of rules for mailing list contribution as for poky/oe-core 
is likely to apply to this git repo, so follow 
https://docs.yoctoproject.org/contributor-guide/submit-changes.html 
(4.5.3 can be skipped).

You probably want to have a look at 
https://docs.yoctoproject.org/contributor-guide/recipe-style-guide.html too.

Cheers,
Quentin