From: Frederic Martinsons <frederic.martinsons@...> This series brings the support of local git repository inside a cargo based recipe. It also enable devtool capacity on it and provide a real crate example recipe to show how things are done. The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf: xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000) are available in the Git repository at: https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool Alex Kiernan (1): cargo_common.bbclass: Support local github repos Frederic Martinsons (4): cargo_common.bbclass: add support of user in url for patch rust-example: provide a recipe for zvariant devtool: add support for multiple git url inside a cargo based recipe patch: support of git patches when the source uri contained subpath param meta/classes-recipe/cargo_common.bbclass | 40 + meta/classes/externalsrc.bbclass | 3 + meta/lib/oe/patch.py | 57 +- .../rust-example/zvariant-crates.inc | 145 ++ .../0001-Tweak-zvariant-cargo-config.patch | 1249 +++++++++++++++++ .../rust-example/zvariant_3.12.0.bb | 20 + 6 files changed, 1501 insertions(+), 13 deletions(-) create mode 100644 meta/recipes-extended/rust-example/zvariant-crates.inc create mode 100644 meta/recipes-extended/rust-example/zvariant/0001-Tweak-zvariant-cargo-config.patch create mode 100644 meta/recipes-extended/rust-example/zvariant_3.12.0.bb -- 2.34.1
|
|
On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote: From: Frederic Martinsons <frederic.martinsons@...>
This series brings the support of local git repository inside a cargo based recipe.
It also enable devtool capacity on it and provide a real crate example recipe to show how things are done.
The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
are available in the Git repository at:
https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
Alex Kiernan (1): cargo_common.bbclass: Support local github repos
Frederic Martinsons (4): cargo_common.bbclass: add support of user in url for patch rust-example: provide a recipe for zvariant devtool: add support for multiple git url inside a cargo based recipe patch: support of git patches when the source uri contained subpath param The various rust/cargo/crate patches look like they're heading in a good direction, thanks! The one thing which I think is missing is more support for testing some of these changes in our automated testing. In particular, devtool does have a decent test suite so we should ensure new devtool additions have tests. You can see the devtools tests in meta/lib/oeqa/selftest/cases/devtool.py and run them with a command like "oe-selftest -r devtool -j 3" for example. Cheers, Richard
|
|
So if devtool tests would operate on zvariant recipe, then the recipe can simply go into meta-selftest after all :) Alex On Mon, 27 Mar 2023 at 16:20, Richard Purdie <richard.purdie@...> wrote: On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
From: Frederic Martinsons <frederic.martinsons@...>
This series brings the support of local git repository inside a cargo based recipe.
It also enable devtool capacity on it and provide a real crate example recipe to show how things are done.
The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
are available in the Git repository at:
https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
Alex Kiernan (1): cargo_common.bbclass: Support local github repos
Frederic Martinsons (4): cargo_common.bbclass: add support of user in url for patch rust-example: provide a recipe for zvariant devtool: add support for multiple git url inside a cargo based recipe patch: support of git patches when the source uri contained subpath param The various rust/cargo/crate patches look like they're heading in a good direction, thanks!
The one thing which I think is missing is more support for testing some of these changes in our automated testing.
In particular, devtool does have a decent test suite so we should ensure new devtool additions have tests.
You can see the devtools tests in meta/lib/oeqa/selftest/cases/devtool.py and run them with a command like "oe-selftest -r devtool -j 3" for example.
Cheers,
Richard
|
|
Ah!
Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant. I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
Thank you all for the advices.
toggle quoted message
Show quoted text
So if devtool tests would operate on zvariant recipe, then the recipe
can simply go into meta-selftest after all :)
Alex
On Mon, 27 Mar 2023 at 16:20, Richard Purdie
<richard.purdie@...> wrote:
>
> On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
> > From: Frederic Martinsons <frederic.martinsons@...>
> >
> > This series brings the support of local git repository inside
> > a cargo based recipe.
> >
> > It also enable devtool capacity on it and provide a real crate
> > example recipe to show how things are done.
> >
> > The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
> >
> > xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
> >
> > are available in the Git repository at:
> >
> > https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
> >
> > Alex Kiernan (1):
> > cargo_common.bbclass: Support local github repos
> >
> > Frederic Martinsons (4):
> > cargo_common.bbclass: add support of user in url for patch
> > rust-example: provide a recipe for zvariant
> > devtool: add support for multiple git url inside a cargo based recipe
> > patch: support of git patches when the source uri contained subpath
> > param
>
> The various rust/cargo/crate patches look like they're heading in a
> good direction, thanks!
>
> The one thing which I think is missing is more support for testing some
> of these changes in our automated testing.
>
> In particular, devtool does have a decent test suite so we should
> ensure new devtool additions have tests.
>
> You can see the devtools tests in
> meta/lib/oeqa/selftest/cases/devtool.py and run them with a command
> like "oe-selftest -r devtool -j 3" for example.
>
> Cheers,
>
> Richard
>
>
>
|
|
If you'd like to do more here's off the top of my head: - enable rust kernel modules in linux-yocto-dev - help Alex Kiernan with update 1.67 -> 1.68; we need as many people as possible capable of updating the rust toolchain. It's often not trivial: https://lists.openembedded.org/g/openembedded-core/message/178272Alex On Mon, 27 Mar 2023 at 17:01, Frédéric Martinsons <frederic.martinsons@...> wrote: Ah!
Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant. I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
Thank you all for the advices.
Le lun. 27 mars 2023, 16:25, Alexander Kanavin <alex.kanavin@...> a écrit :
So if devtool tests would operate on zvariant recipe, then the recipe can simply go into meta-selftest after all :)
Alex
On Mon, 27 Mar 2023 at 16:20, Richard Purdie <richard.purdie@...> wrote:
On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
From: Frederic Martinsons <frederic.martinsons@...>
This series brings the support of local git repository inside a cargo based recipe.
It also enable devtool capacity on it and provide a real crate example recipe to show how things are done.
The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
are available in the Git repository at:
https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
Alex Kiernan (1): cargo_common.bbclass: Support local github repos
Frederic Martinsons (4): cargo_common.bbclass: add support of user in url for patch rust-example: provide a recipe for zvariant devtool: add support for multiple git url inside a cargo based recipe patch: support of git patches when the source uri contained subpath param The various rust/cargo/crate patches look like they're heading in a good direction, thanks!
The one thing which I think is missing is more support for testing some of these changes in our automated testing.
In particular, devtool does have a decent test suite so we should ensure new devtool additions have tests.
You can see the devtools tests in meta/lib/oeqa/selftest/cases/devtool.py and run them with a command like "oe-selftest -r devtool -j 3" for example.
Cheers,
Richard
|
|
I'll look at this but I'm not sure if I can help since I'm a beginner (enthusiastic but still)
toggle quoted message
Show quoted text
If you'd like to do more here's off the top of my head:
- enable rust kernel modules in linux-yocto-dev
- help Alex Kiernan with update 1.67 -> 1.68; we need as many people
as possible capable of updating the rust toolchain. It's often not
trivial:
https://lists.openembedded.org/g/openembedded-core/message/178272
Alex
On Mon, 27 Mar 2023 at 17:01, Frédéric Martinsons
<frederic.martinsons@...> wrote:
>
> Ah!
>
> Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant.
> I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
>
> I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
>
> Thank you all for the advices.
>
> Le lun. 27 mars 2023, 16:25, Alexander Kanavin <alex.kanavin@...> a écrit :
>>
>> So if devtool tests would operate on zvariant recipe, then the recipe
>> can simply go into meta-selftest after all :)
>>
>> Alex
>>
>> On Mon, 27 Mar 2023 at 16:20, Richard Purdie
>> <richard.purdie@...> wrote:
>> >
>> > On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
>> > > From: Frederic Martinsons <frederic.martinsons@...>
>> > >
>> > > This series brings the support of local git repository inside
>> > > a cargo based recipe.
>> > >
>> > > It also enable devtool capacity on it and provide a real crate
>> > > example recipe to show how things are done.
>> > >
>> > > The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
>> > >
>> > > xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
>> > >
>> > > are available in the Git repository at:
>> > >
>> > > https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
>> > >
>> > > Alex Kiernan (1):
>> > > cargo_common.bbclass: Support local github repos
>> > >
>> > > Frederic Martinsons (4):
>> > > cargo_common.bbclass: add support of user in url for patch
>> > > rust-example: provide a recipe for zvariant
>> > > devtool: add support for multiple git url inside a cargo based recipe
>> > > patch: support of git patches when the source uri contained subpath
>> > > param
>> >
>> > The various rust/cargo/crate patches look like they're heading in a
>> > good direction, thanks!
>> >
>> > The one thing which I think is missing is more support for testing some
>> > of these changes in our automated testing.
>> >
>> > In particular, devtool does have a decent test suite so we should
>> > ensure new devtool additions have tests.
>> >
>> > You can see the devtools tests in
>> > meta/lib/oeqa/selftest/cases/devtool.py and run them with a command
>> > like "oe-selftest -r devtool -j 3" for example.
>> >
>> > Cheers,
>> >
>> > Richard
>> >
>> >
>> >
|
|
Updating the rust version is pretty much nothing to do with your rust knowledge and way more about digging into how the bootstrap process hangs together... whilst I have an awesome rustacean working for me, I don't think I've ever had to drag him into helping with an upgrade. I wish I could say I'd spent the last few weeks figuring out why the upgrade broke, but I've been buried down the bottom of an ESP-IDF application... Alex On Mon, Mar 27, 2023 at 7:08 PM Frédéric Martinsons <frederic.martinsons@...> wrote: I'll look at this but I'm not sure if I can help since I'm a beginner (enthusiastic but still)
Le lun. 27 mars 2023, 19:19, Alexander Kanavin <alex.kanavin@...> a écrit :
If you'd like to do more here's off the top of my head:
- enable rust kernel modules in linux-yocto-dev
- help Alex Kiernan with update 1.67 -> 1.68; we need as many people as possible capable of updating the rust toolchain. It's often not trivial: https://lists.openembedded.org/g/openembedded-core/message/178272
Alex
On Mon, 27 Mar 2023 at 17:01, Frédéric Martinsons <frederic.martinsons@...> wrote:
Ah!
Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant. I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
Thank you all for the advices.
Le lun. 27 mars 2023, 16:25, Alexander Kanavin <alex.kanavin@...> a écrit :
So if devtool tests would operate on zvariant recipe, then the recipe can simply go into meta-selftest after all :)
Alex
On Mon, 27 Mar 2023 at 16:20, Richard Purdie <richard.purdie@...> wrote:
On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
From: Frederic Martinsons <frederic.martinsons@...>
This series brings the support of local git repository inside a cargo based recipe.
It also enable devtool capacity on it and provide a real crate example recipe to show how things are done.
The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
are available in the Git repository at:
https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
Alex Kiernan (1): cargo_common.bbclass: Support local github repos
Frederic Martinsons (4): cargo_common.bbclass: add support of user in url for patch rust-example: provide a recipe for zvariant devtool: add support for multiple git url inside a cargo based recipe patch: support of git patches when the source uri contained subpath param The various rust/cargo/crate patches look like they're heading in a good direction, thanks!
The one thing which I think is missing is more support for testing some of these changes in our automated testing.
In particular, devtool does have a decent test suite so we should ensure new devtool additions have tests.
You can see the devtools tests in meta/lib/oeqa/selftest/cases/devtool.py and run them with a command like "oe-selftest -r devtool -j 3" for example.
Cheers,
Richard
-- Alex Kiernan
|
|
Ok great, I'm willing to know more about the bootstrap of a rust toolchain, I think I can start by just upgrading my poky master to rust 1.68 and see what it spills out when I compile the hello world
toggle quoted message
Show quoted text
On the other hand, for enabling rust kernel modules in linux-yocto-dev, I don't know where to start (full disclosure : I have no skills about kernel and kernel module developments) Updating the rust version is pretty much nothing to do with your rust
knowledge and way more about digging into how the bootstrap process
hangs together... whilst I have an awesome rustacean working for me, I
don't think I've ever had to drag him into helping with an upgrade.
I wish I could say I'd spent the last few weeks figuring out why the
upgrade broke, but I've been buried down the bottom of an ESP-IDF
application...
Alex
On Mon, Mar 27, 2023 at 7:08 PM Frédéric Martinsons
<frederic.martinsons@...> wrote:
>
> I'll look at this but I'm not sure if I can help since I'm a beginner (enthusiastic but still)
>
> Le lun. 27 mars 2023, 19:19, Alexander Kanavin <alex.kanavin@...> a écrit :
>>
>> If you'd like to do more here's off the top of my head:
>>
>> - enable rust kernel modules in linux-yocto-dev
>>
>> - help Alex Kiernan with update 1.67 -> 1.68; we need as many people
>> as possible capable of updating the rust toolchain. It's often not
>> trivial:
>> https://lists.openembedded.org/g/openembedded-core/message/178272
>>
>> Alex
>>
>> On Mon, 27 Mar 2023 at 17:01, Frédéric Martinsons
>> <frederic.martinsons@...> wrote:
>> >
>> > Ah!
>> >
>> > Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant.
>> > I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
>> >
>> > I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
>> >
>> > Thank you all for the advices.
>> >
>> > Le lun. 27 mars 2023, 16:25, Alexander Kanavin <alex.kanavin@...> a écrit :
>> >>
>> >> So if devtool tests would operate on zvariant recipe, then the recipe
>> >> can simply go into meta-selftest after all :)
>> >>
>> >> Alex
>> >>
>> >> On Mon, 27 Mar 2023 at 16:20, Richard Purdie
>> >> <richard.purdie@...> wrote:
>> >> >
>> >> > On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
>> >> > > From: Frederic Martinsons <frederic.martinsons@...>
>> >> > >
>> >> > > This series brings the support of local git repository inside
>> >> > > a cargo based recipe.
>> >> > >
>> >> > > It also enable devtool capacity on it and provide a real crate
>> >> > > example recipe to show how things are done.
>> >> > >
>> >> > > The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
>> >> > >
>> >> > > xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
>> >> > >
>> >> > > are available in the Git repository at:
>> >> > >
>> >> > > https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
>> >> > >
>> >> > > Alex Kiernan (1):
>> >> > > cargo_common.bbclass: Support local github repos
>> >> > >
>> >> > > Frederic Martinsons (4):
>> >> > > cargo_common.bbclass: add support of user in url for patch
>> >> > > rust-example: provide a recipe for zvariant
>> >> > > devtool: add support for multiple git url inside a cargo based recipe
>> >> > > patch: support of git patches when the source uri contained subpath
>> >> > > param
>> >> >
>> >> > The various rust/cargo/crate patches look like they're heading in a
>> >> > good direction, thanks!
>> >> >
>> >> > The one thing which I think is missing is more support for testing some
>> >> > of these changes in our automated testing.
>> >> >
>> >> > In particular, devtool does have a decent test suite so we should
>> >> > ensure new devtool additions have tests.
>> >> >
>> >> > You can see the devtools tests in
>> >> > meta/lib/oeqa/selftest/cases/devtool.py and run them with a command
>> >> > like "oe-selftest -r devtool -j 3" for example.
>> >> >
>> >> > Cheers,
>> >> >
>> >> > Richard
>> >> >
>> >> >
>> >> >
--
Alex Kiernan
|
|
IIRC the cross upgrade just works, its the target build which explodes: https://github.com/akiernan/openembedded-coreOn Mon, Mar 27, 2023 at 7:40 PM Frédéric Martinsons <frederic.martinsons@...> wrote: Ok great, I'm willing to know more about the bootstrap of a rust toolchain, I think I can start by just upgrading my poky master to rust 1.68 and see what it spills out when I compile the hello world
On the other hand, for enabling rust kernel modules in linux-yocto-dev, I don't know where to start (full disclosure : I have no skills about kernel and kernel module developments)
Le lun. 27 mars 2023, 20:30, Alex Kiernan <alex.kiernan@...> a écrit :
Updating the rust version is pretty much nothing to do with your rust knowledge and way more about digging into how the bootstrap process hangs together... whilst I have an awesome rustacean working for me, I don't think I've ever had to drag him into helping with an upgrade.
I wish I could say I'd spent the last few weeks figuring out why the upgrade broke, but I've been buried down the bottom of an ESP-IDF application...
Alex
On Mon, Mar 27, 2023 at 7:08 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
I'll look at this but I'm not sure if I can help since I'm a beginner (enthusiastic but still)
Le lun. 27 mars 2023, 19:19, Alexander Kanavin <alex.kanavin@...> a écrit :
If you'd like to do more here's off the top of my head:
- enable rust kernel modules in linux-yocto-dev
- help Alex Kiernan with update 1.67 -> 1.68; we need as many people as possible capable of updating the rust toolchain. It's often not trivial: https://lists.openembedded.org/g/openembedded-core/message/178272
Alex
On Mon, 27 Mar 2023 at 17:01, Frédéric Martinsons <frederic.martinsons@...> wrote:
Ah!
Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant. I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
Thank you all for the advices.
Le lun. 27 mars 2023, 16:25, Alexander Kanavin <alex.kanavin@...> a écrit :
So if devtool tests would operate on zvariant recipe, then the recipe can simply go into meta-selftest after all :)
Alex
On Mon, 27 Mar 2023 at 16:20, Richard Purdie <richard.purdie@...> wrote:
On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
From: Frederic Martinsons <frederic.martinsons@...>
This series brings the support of local git repository inside a cargo based recipe.
It also enable devtool capacity on it and provide a real crate example recipe to show how things are done.
The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
are available in the Git repository at:
https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
Alex Kiernan (1): cargo_common.bbclass: Support local github repos
Frederic Martinsons (4): cargo_common.bbclass: add support of user in url for patch rust-example: provide a recipe for zvariant devtool: add support for multiple git url inside a cargo based recipe patch: support of git patches when the source uri contained subpath param The various rust/cargo/crate patches look like they're heading in a good direction, thanks!
The one thing which I think is missing is more support for testing some of these changes in our automated testing.
In particular, devtool does have a decent test suite so we should ensure new devtool additions have tests.
You can see the devtools tests in meta/lib/oeqa/selftest/cases/devtool.py and run them with a command like "oe-selftest -r devtool -j 3" for example.
Cheers,
Richard
-- Alex Kiernan
-- Alex Kiernan
|
|
toggle quoted message
Show quoted text
On Mon, 27 Mar 2023 at 20:52, Alex Kiernan <alex.kiernan@...> wrote: IIRC the cross upgrade just works, its the target build which explodes:
https://github.com/akiernan/openembedded-core
On Mon, Mar 27, 2023 at 7:40 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
Ok great, I'm willing to know more about the bootstrap of a rust toolchain, I think I can start by just upgrading my poky master to rust 1.68 and see what it spills out when I compile the hello world
On the other hand, for enabling rust kernel modules in linux-yocto-dev, I don't know where to start (full disclosure : I have no skills about kernel and kernel module developments)
Le lun. 27 mars 2023, 20:30, Alex Kiernan <alex.kiernan@...> a écrit :
Updating the rust version is pretty much nothing to do with your rust knowledge and way more about digging into how the bootstrap process hangs together... whilst I have an awesome rustacean working for me, I don't think I've ever had to drag him into helping with an upgrade.
I wish I could say I'd spent the last few weeks figuring out why the upgrade broke, but I've been buried down the bottom of an ESP-IDF application...
Alex
On Mon, Mar 27, 2023 at 7:08 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
I'll look at this but I'm not sure if I can help since I'm a beginner (enthusiastic but still)
Le lun. 27 mars 2023, 19:19, Alexander Kanavin <alex.kanavin@...> a écrit :
If you'd like to do more here's off the top of my head:
- enable rust kernel modules in linux-yocto-dev
- help Alex Kiernan with update 1.67 -> 1.68; we need as many people as possible capable of updating the rust toolchain. It's often not trivial: https://lists.openembedded.org/g/openembedded-core/message/178272
Alex
On Mon, 27 Mar 2023 at 17:01, Frédéric Martinsons <frederic.martinsons@...> wrote:
Ah!
Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant. I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
Thank you all for the advices.
Le lun. 27 mars 2023, 16:25, Alexander Kanavin <alex.kanavin@...> a écrit :
So if devtool tests would operate on zvariant recipe, then the recipe can simply go into meta-selftest after all :)
Alex
On Mon, 27 Mar 2023 at 16:20, Richard Purdie <richard.purdie@...> wrote:
On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
From: Frederic Martinsons <frederic.martinsons@...>
This series brings the support of local git repository inside a cargo based recipe.
It also enable devtool capacity on it and provide a real crate example recipe to show how things are done.
The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
are available in the Git repository at:
https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
Alex Kiernan (1): cargo_common.bbclass: Support local github repos
Frederic Martinsons (4): cargo_common.bbclass: add support of user in url for patch rust-example: provide a recipe for zvariant devtool: add support for multiple git url inside a cargo based recipe patch: support of git patches when the source uri contained subpath param The various rust/cargo/crate patches look like they're heading in a good direction, thanks!
The one thing which I think is missing is more support for testing some of these changes in our automated testing.
In particular, devtool does have a decent test suite so we should ensure new devtool additions have tests.
You can see the devtools tests in meta/lib/oeqa/selftest/cases/devtool.py and run them with a command like "oe-selftest -r devtool -j 3" for example.
Cheers,
Richard
-- Alex Kiernan
-- Alex Kiernan
|
|
Thank you alex and alexender ;)
I'll take a look at this as soon as possible and and tell you in a dedicated thread if I'm making progress. But first, I'll work for the devtool test that has been mentioned first.
Have a good evening (or day, depending on your timezone)
toggle quoted message
Show quoted text
For the kernel modules you could start by replicating an out-of-yocto
kernel build as shown here:
https://lwn.net/Articles/910762/
Alex
On Mon, 27 Mar 2023 at 20:52, Alex Kiernan <alex.kiernan@...> wrote:
>
> IIRC the cross upgrade just works, its the target build which explodes:
>
> https://github.com/akiernan/openembedded-core
>
> On Mon, Mar 27, 2023 at 7:40 PM Frédéric Martinsons
> <frederic.martinsons@...> wrote:
> >
> > Ok great, I'm willing to know more about the bootstrap of a rust toolchain, I think I can start by just upgrading my poky master to rust 1.68 and see what it spills out when I compile the hello world
> >
> > On the other hand, for enabling rust kernel modules in linux-yocto-dev, I don't know where to start (full disclosure : I have no skills about kernel and kernel module developments)
> >
> > Le lun. 27 mars 2023, 20:30, Alex Kiernan <alex.kiernan@...> a écrit :
> >>
> >> Updating the rust version is pretty much nothing to do with your rust
> >> knowledge and way more about digging into how the bootstrap process
> >> hangs together... whilst I have an awesome rustacean working for me, I
> >> don't think I've ever had to drag him into helping with an upgrade.
> >>
> >> I wish I could say I'd spent the last few weeks figuring out why the
> >> upgrade broke, but I've been buried down the bottom of an ESP-IDF
> >> application...
> >>
> >> Alex
> >>
> >> On Mon, Mar 27, 2023 at 7:08 PM Frédéric Martinsons
> >> <frederic.martinsons@...> wrote:
> >> >
> >> > I'll look at this but I'm not sure if I can help since I'm a beginner (enthusiastic but still)
> >> >
> >> > Le lun. 27 mars 2023, 19:19, Alexander Kanavin <alex.kanavin@...> a écrit :
> >> >>
> >> >> If you'd like to do more here's off the top of my head:
> >> >>
> >> >> - enable rust kernel modules in linux-yocto-dev
> >> >>
> >> >> - help Alex Kiernan with update 1.67 -> 1.68; we need as many people
> >> >> as possible capable of updating the rust toolchain. It's often not
> >> >> trivial:
> >> >> https://lists.openembedded.org/g/openembedded-core/message/178272
> >> >>
> >> >> Alex
> >> >>
> >> >> On Mon, 27 Mar 2023 at 17:01, Frédéric Martinsons
> >> >> <frederic.martinsons@...> wrote:
> >> >> >
> >> >> > Ah!
> >> >> >
> >> >> > Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant.
> >> >> > I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
> >> >> >
> >> >> > I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
> >> >> >
> >> >> > Thank you all for the advices.
> >> >> >
> >> >> > Le lun. 27 mars 2023, 16:25, Alexander Kanavin <alex.kanavin@...> a écrit :
> >> >> >>
> >> >> >> So if devtool tests would operate on zvariant recipe, then the recipe
> >> >> >> can simply go into meta-selftest after all :)
> >> >> >>
> >> >> >> Alex
> >> >> >>
> >> >> >> On Mon, 27 Mar 2023 at 16:20, Richard Purdie
> >> >> >> <richard.purdie@...> wrote:
> >> >> >> >
> >> >> >> > On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
> >> >> >> > > From: Frederic Martinsons <frederic.martinsons@...>
> >> >> >> > >
> >> >> >> > > This series brings the support of local git repository inside
> >> >> >> > > a cargo based recipe.
> >> >> >> > >
> >> >> >> > > It also enable devtool capacity on it and provide a real crate
> >> >> >> > > example recipe to show how things are done.
> >> >> >> > >
> >> >> >> > > The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
> >> >> >> > >
> >> >> >> > > xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
> >> >> >> > >
> >> >> >> > > are available in the Git repository at:
> >> >> >> > >
> >> >> >> > > https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
> >> >> >> > >
> >> >> >> > > Alex Kiernan (1):
> >> >> >> > > cargo_common.bbclass: Support local github repos
> >> >> >> > >
> >> >> >> > > Frederic Martinsons (4):
> >> >> >> > > cargo_common.bbclass: add support of user in url for patch
> >> >> >> > > rust-example: provide a recipe for zvariant
> >> >> >> > > devtool: add support for multiple git url inside a cargo based recipe
> >> >> >> > > patch: support of git patches when the source uri contained subpath
> >> >> >> > > param
> >> >> >> >
> >> >> >> > The various rust/cargo/crate patches look like they're heading in a
> >> >> >> > good direction, thanks!
> >> >> >> >
> >> >> >> > The one thing which I think is missing is more support for testing some
> >> >> >> > of these changes in our automated testing.
> >> >> >> >
> >> >> >> > In particular, devtool does have a decent test suite so we should
> >> >> >> > ensure new devtool additions have tests.
> >> >> >> >
> >> >> >> > You can see the devtools tests in
> >> >> >> > meta/lib/oeqa/selftest/cases/devtool.py and run them with a command
> >> >> >> > like "oe-selftest -r devtool -j 3" for example.
> >> >> >> >
> >> >> >> > Cheers,
> >> >> >> >
> >> >> >> > Richard
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >>
> >>
> >>
> >> --
> >> Alex Kiernan
>
>
>
> --
> Alex Kiernan
|
|
I think I have meanwhile resolved the 1.68 upgrade issues: https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/package-version-updatesSo that leaves the hip and cool rust-in-kernel project ;-) Alex On Mon, 27 Mar 2023 at 21:20, Frédéric Martinsons <frederic.martinsons@...> wrote: Thank you alex and alexender ;)
I'll take a look at this as soon as possible and and tell you in a dedicated thread if I'm making progress. But first, I'll work for the devtool test that has been mentioned first.
Have a good evening (or day, depending on your timezone)
Le lun. 27 mars 2023, 21:00, Alexander Kanavin <alex.kanavin@...> a écrit :
For the kernel modules you could start by replicating an out-of-yocto kernel build as shown here: https://lwn.net/Articles/910762/
Alex
On Mon, 27 Mar 2023 at 20:52, Alex Kiernan <alex.kiernan@...> wrote:
IIRC the cross upgrade just works, its the target build which explodes:
https://github.com/akiernan/openembedded-core
On Mon, Mar 27, 2023 at 7:40 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
Ok great, I'm willing to know more about the bootstrap of a rust toolchain, I think I can start by just upgrading my poky master to rust 1.68 and see what it spills out when I compile the hello world
On the other hand, for enabling rust kernel modules in linux-yocto-dev, I don't know where to start (full disclosure : I have no skills about kernel and kernel module developments)
Le lun. 27 mars 2023, 20:30, Alex Kiernan <alex.kiernan@...> a écrit :
Updating the rust version is pretty much nothing to do with your rust knowledge and way more about digging into how the bootstrap process hangs together... whilst I have an awesome rustacean working for me, I don't think I've ever had to drag him into helping with an upgrade.
I wish I could say I'd spent the last few weeks figuring out why the upgrade broke, but I've been buried down the bottom of an ESP-IDF application...
Alex
On Mon, Mar 27, 2023 at 7:08 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
I'll look at this but I'm not sure if I can help since I'm a beginner (enthusiastic but still)
Le lun. 27 mars 2023, 19:19, Alexander Kanavin <alex.kanavin@...> a écrit :
If you'd like to do more here's off the top of my head:
- enable rust kernel modules in linux-yocto-dev
- help Alex Kiernan with update 1.67 -> 1.68; we need as many people as possible capable of updating the rust toolchain. It's often not trivial: https://lists.openembedded.org/g/openembedded-core/message/178272
Alex
On Mon, 27 Mar 2023 at 17:01, Frédéric Martinsons <frederic.martinsons@...> wrote:
Ah!
Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant. I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
Thank you all for the advices.
Le lun. 27 mars 2023, 16:25, Alexander Kanavin <alex.kanavin@...> a écrit :
So if devtool tests would operate on zvariant recipe, then the recipe can simply go into meta-selftest after all :)
Alex
On Mon, 27 Mar 2023 at 16:20, Richard Purdie <richard.purdie@...> wrote:
On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
From: Frederic Martinsons <frederic.martinsons@...>
This series brings the support of local git repository inside a cargo based recipe.
It also enable devtool capacity on it and provide a real crate example recipe to show how things are done.
The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
are available in the Git repository at:
https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
Alex Kiernan (1): cargo_common.bbclass: Support local github repos
Frederic Martinsons (4): cargo_common.bbclass: add support of user in url for patch rust-example: provide a recipe for zvariant devtool: add support for multiple git url inside a cargo based recipe patch: support of git patches when the source uri contained subpath param The various rust/cargo/crate patches look like they're heading in a good direction, thanks!
The one thing which I think is missing is more support for testing some of these changes in our automated testing.
In particular, devtool does have a decent test suite so we should ensure new devtool additions have tests.
You can see the devtools tests in meta/lib/oeqa/selftest/cases/devtool.py and run them with a command like "oe-selftest -r devtool -j 3" for example.
Cheers,
Richard
-- Alex Kiernan
-- Alex Kiernan
|
|
I was going to say, that looks pretty much identical to what I had, but it looks like they've reverted some LTO stuff in 1.68.1, which I guess is what was exploding: https://github.com/rust-lang/rust/issues/109067Would be good to pick up this too: https://github.com/akiernan/openembedded-core/commit/9e098599aa5247086a346bf73a087a2ce4ab640f#diff-84ec9441385da6fa39407418d2eebc685e1ca4260bfeb94c6f5d411ef706df1ewhich was a backport of what actually got merged upstream for @Khem Raj's open64 fix: On Mon, Mar 27, 2023 at 11:13 PM Alexander Kanavin <alex.kanavin@...> wrote: I think I have meanwhile resolved the 1.68 upgrade issues: https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/package-version-updates
So that leaves the hip and cool rust-in-kernel project ;-)
Alex
On Mon, 27 Mar 2023 at 21:20, Frédéric Martinsons <frederic.martinsons@...> wrote:
Thank you alex and alexender ;)
I'll take a look at this as soon as possible and and tell you in a dedicated thread if I'm making progress. But first, I'll work for the devtool test that has been mentioned first.
Have a good evening (or day, depending on your timezone)
Le lun. 27 mars 2023, 21:00, Alexander Kanavin <alex.kanavin@...> a écrit :
For the kernel modules you could start by replicating an out-of-yocto kernel build as shown here: https://lwn.net/Articles/910762/
Alex
On Mon, 27 Mar 2023 at 20:52, Alex Kiernan <alex.kiernan@...> wrote:
IIRC the cross upgrade just works, its the target build which explodes:
https://github.com/akiernan/openembedded-core
On Mon, Mar 27, 2023 at 7:40 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
Ok great, I'm willing to know more about the bootstrap of a rust toolchain, I think I can start by just upgrading my poky master to rust 1.68 and see what it spills out when I compile the hello world
On the other hand, for enabling rust kernel modules in linux-yocto-dev, I don't know where to start (full disclosure : I have no skills about kernel and kernel module developments)
Le lun. 27 mars 2023, 20:30, Alex Kiernan <alex.kiernan@...> a écrit :
Updating the rust version is pretty much nothing to do with your rust knowledge and way more about digging into how the bootstrap process hangs together... whilst I have an awesome rustacean working for me, I don't think I've ever had to drag him into helping with an upgrade.
I wish I could say I'd spent the last few weeks figuring out why the upgrade broke, but I've been buried down the bottom of an ESP-IDF application...
Alex
On Mon, Mar 27, 2023 at 7:08 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
I'll look at this but I'm not sure if I can help since I'm a beginner (enthusiastic but still)
Le lun. 27 mars 2023, 19:19, Alexander Kanavin <alex.kanavin@...> a écrit :
If you'd like to do more here's off the top of my head:
- enable rust kernel modules in linux-yocto-dev
- help Alex Kiernan with update 1.67 -> 1.68; we need as many people as possible capable of updating the rust toolchain. It's often not trivial: https://lists.openembedded.org/g/openembedded-core/message/178272
Alex
On Mon, 27 Mar 2023 at 17:01, Frédéric Martinsons <frederic.martinsons@...> wrote:
Ah!
Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant. I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
Thank you all for the advices.
Le lun. 27 mars 2023, 16:25, Alexander Kanavin <alex.kanavin@...> a écrit :
So if devtool tests would operate on zvariant recipe, then the recipe can simply go into meta-selftest after all :)
Alex
On Mon, 27 Mar 2023 at 16:20, Richard Purdie <richard.purdie@...> wrote:
On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
From: Frederic Martinsons <frederic.martinsons@...>
This series brings the support of local git repository inside a cargo based recipe.
It also enable devtool capacity on it and provide a real crate example recipe to show how things are done.
The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
are available in the Git repository at:
https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
Alex Kiernan (1): cargo_common.bbclass: Support local github repos
Frederic Martinsons (4): cargo_common.bbclass: add support of user in url for patch rust-example: provide a recipe for zvariant devtool: add support for multiple git url inside a cargo based recipe patch: support of git patches when the source uri contained subpath param The various rust/cargo/crate patches look like they're heading in a good direction, thanks!
The one thing which I think is missing is more support for testing some of these changes in our automated testing.
In particular, devtool does have a decent test suite so we should ensure new devtool additions have tests.
You can see the devtools tests in meta/lib/oeqa/selftest/cases/devtool.py and run them with a command like "oe-selftest -r devtool -j 3" for example.
Cheers,
Richard
-- Alex Kiernan
-- Alex Kiernan
-- Alex Kiernan
|
|
The exploding part was the 'unable to find std crate', which is fixed by not doing 'build --stage 2' at all, and going directly to 'install' (which builds all the needed parts in correct order anyway and is tested upstream).
I'll add the getrandom-open64.patch update to my tree, thanks.
Alex
toggle quoted message
Show quoted text
On Tue, 28 Mar 2023 at 09:11, Alex Kiernan <alex.kiernan@...> wrote: I was going to say, that looks pretty much identical to what I had, but it looks like they've reverted some LTO stuff in 1.68.1, which I guess is what was exploding:
https://github.com/rust-lang/rust/issues/109067
Would be good to pick up this too:
https://github.com/akiernan/openembedded-core/commit/9e098599aa5247086a346bf73a087a2ce4ab640f#diff-84ec9441385da6fa39407418d2eebc685e1ca4260bfeb94c6f5d411ef706df1e
which was a backport of what actually got merged upstream for @Khem Raj's open64 fix:
On Mon, Mar 27, 2023 at 11:13 PM Alexander Kanavin <alex.kanavin@...> wrote:
I think I have meanwhile resolved the 1.68 upgrade issues: https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/package-version-updates
So that leaves the hip and cool rust-in-kernel project ;-)
Alex
On Mon, 27 Mar 2023 at 21:20, Frédéric Martinsons <frederic.martinsons@...> wrote:
Thank you alex and alexender ;)
I'll take a look at this as soon as possible and and tell you in a dedicated thread if I'm making progress. But first, I'll work for the devtool test that has been mentioned first.
Have a good evening (or day, depending on your timezone)
Le lun. 27 mars 2023, 21:00, Alexander Kanavin <alex.kanavin@...> a écrit :
For the kernel modules you could start by replicating an out-of-yocto kernel build as shown here: https://lwn.net/Articles/910762/
Alex
On Mon, 27 Mar 2023 at 20:52, Alex Kiernan <alex.kiernan@...> wrote:
IIRC the cross upgrade just works, its the target build which explodes:
https://github.com/akiernan/openembedded-core
On Mon, Mar 27, 2023 at 7:40 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
Ok great, I'm willing to know more about the bootstrap of a rust toolchain, I think I can start by just upgrading my poky master to rust 1.68 and see what it spills out when I compile the hello world
On the other hand, for enabling rust kernel modules in linux-yocto-dev, I don't know where to start (full disclosure : I have no skills about kernel and kernel module developments)
Le lun. 27 mars 2023, 20:30, Alex Kiernan <alex.kiernan@...> a écrit :
Updating the rust version is pretty much nothing to do with your rust knowledge and way more about digging into how the bootstrap process hangs together... whilst I have an awesome rustacean working for me, I don't think I've ever had to drag him into helping with an upgrade.
I wish I could say I'd spent the last few weeks figuring out why the upgrade broke, but I've been buried down the bottom of an ESP-IDF application...
Alex
On Mon, Mar 27, 2023 at 7:08 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
I'll look at this but I'm not sure if I can help since I'm a beginner (enthusiastic but still)
Le lun. 27 mars 2023, 19:19, Alexander Kanavin <alex.kanavin@...> a écrit :
If you'd like to do more here's off the top of my head:
- enable rust kernel modules in linux-yocto-dev
- help Alex Kiernan with update 1.67 -> 1.68; we need as many people as possible capable of updating the rust toolchain. It's often not trivial: https://lists.openembedded.org/g/openembedded-core/message/178272
Alex
On Mon, 27 Mar 2023 at 17:01, Frédéric Martinsons <frederic.martinsons@...> wrote:
Ah!
Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant. I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
Thank you all for the advices.
Le lun. 27 mars 2023, 16:25, Alexander Kanavin <alex.kanavin@...> a écrit :
So if devtool tests would operate on zvariant recipe, then the recipe can simply go into meta-selftest after all :)
Alex
On Mon, 27 Mar 2023 at 16:20, Richard Purdie <richard.purdie@...> wrote:
On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
From: Frederic Martinsons <frederic.martinsons@...>
This series brings the support of local git repository inside a cargo based recipe.
It also enable devtool capacity on it and provide a real crate example recipe to show how things are done.
The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
are available in the Git repository at:
https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
Alex Kiernan (1): cargo_common.bbclass: Support local github repos
Frederic Martinsons (4): cargo_common.bbclass: add support of user in url for patch rust-example: provide a recipe for zvariant devtool: add support for multiple git url inside a cargo based recipe patch: support of git patches when the source uri contained subpath param The various rust/cargo/crate patches look like they're heading in a good direction, thanks!
The one thing which I think is missing is more support for testing some of these changes in our automated testing.
In particular, devtool does have a decent test suite so we should ensure new devtool additions have tests.
You can see the devtools tests in meta/lib/oeqa/selftest/cases/devtool.py and run them with a command like "oe-selftest -r devtool -j 3" for example.
Cheers,
Richard
-- Alex Kiernan
-- Alex Kiernan
-- Alex Kiernan
|
|
Ah! I stared at all of that stuff and failed to spot it, thanks! On Tue, Mar 28, 2023 at 9:37 AM Alexander Kanavin <alex.kanavin@...> wrote: The exploding part was the 'unable to find std crate', which is fixed by not doing 'build --stage 2' at all, and going directly to 'install' (which builds all the needed parts in correct order anyway and is tested upstream).
I'll add the getrandom-open64.patch update to my tree, thanks.
Alex
On Tue, 28 Mar 2023 at 09:11, Alex Kiernan <alex.kiernan@...> wrote:
I was going to say, that looks pretty much identical to what I had, but it looks like they've reverted some LTO stuff in 1.68.1, which I guess is what was exploding:
https://github.com/rust-lang/rust/issues/109067
Would be good to pick up this too:
https://github.com/akiernan/openembedded-core/commit/9e098599aa5247086a346bf73a087a2ce4ab640f#diff-84ec9441385da6fa39407418d2eebc685e1ca4260bfeb94c6f5d411ef706df1e
which was a backport of what actually got merged upstream for @Khem Raj's open64 fix:
On Mon, Mar 27, 2023 at 11:13 PM Alexander Kanavin <alex.kanavin@...> wrote:
I think I have meanwhile resolved the 1.68 upgrade issues: https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/package-version-updates
So that leaves the hip and cool rust-in-kernel project ;-)
Alex
On Mon, 27 Mar 2023 at 21:20, Frédéric Martinsons <frederic.martinsons@...> wrote:
Thank you alex and alexender ;)
I'll take a look at this as soon as possible and and tell you in a dedicated thread if I'm making progress. But first, I'll work for the devtool test that has been mentioned first.
Have a good evening (or day, depending on your timezone)
Le lun. 27 mars 2023, 21:00, Alexander Kanavin <alex.kanavin@...> a écrit :
For the kernel modules you could start by replicating an out-of-yocto kernel build as shown here: https://lwn.net/Articles/910762/
Alex
On Mon, 27 Mar 2023 at 20:52, Alex Kiernan <alex.kiernan@...> wrote:
IIRC the cross upgrade just works, its the target build which explodes:
https://github.com/akiernan/openembedded-core
On Mon, Mar 27, 2023 at 7:40 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
Ok great, I'm willing to know more about the bootstrap of a rust toolchain, I think I can start by just upgrading my poky master to rust 1.68 and see what it spills out when I compile the hello world
On the other hand, for enabling rust kernel modules in linux-yocto-dev, I don't know where to start (full disclosure : I have no skills about kernel and kernel module developments)
Le lun. 27 mars 2023, 20:30, Alex Kiernan <alex.kiernan@...> a écrit :
Updating the rust version is pretty much nothing to do with your rust knowledge and way more about digging into how the bootstrap process hangs together... whilst I have an awesome rustacean working for me, I don't think I've ever had to drag him into helping with an upgrade.
I wish I could say I'd spent the last few weeks figuring out why the upgrade broke, but I've been buried down the bottom of an ESP-IDF application...
Alex
On Mon, Mar 27, 2023 at 7:08 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
I'll look at this but I'm not sure if I can help since I'm a beginner (enthusiastic but still)
Le lun. 27 mars 2023, 19:19, Alexander Kanavin <alex.kanavin@...> a écrit :
If you'd like to do more here's off the top of my head:
- enable rust kernel modules in linux-yocto-dev
- help Alex Kiernan with update 1.67 -> 1.68; we need as many people as possible capable of updating the rust toolchain. It's often not trivial: https://lists.openembedded.org/g/openembedded-core/message/178272
Alex
On Mon, 27 Mar 2023 at 17:01, Frédéric Martinsons <frederic.martinsons@...> wrote:
Ah!
Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant. I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
Thank you all for the advices.
Le lun. 27 mars 2023, 16:25, Alexander Kanavin <alex.kanavin@...> a écrit :
So if devtool tests would operate on zvariant recipe, then the recipe can simply go into meta-selftest after all :)
Alex
On Mon, 27 Mar 2023 at 16:20, Richard Purdie <richard.purdie@...> wrote:
On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
From: Frederic Martinsons <frederic.martinsons@...>
This series brings the support of local git repository inside a cargo based recipe.
It also enable devtool capacity on it and provide a real crate example recipe to show how things are done.
The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
are available in the Git repository at:
https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
Alex Kiernan (1): cargo_common.bbclass: Support local github repos
Frederic Martinsons (4): cargo_common.bbclass: add support of user in url for patch rust-example: provide a recipe for zvariant devtool: add support for multiple git url inside a cargo based recipe patch: support of git patches when the source uri contained subpath param The various rust/cargo/crate patches look like they're heading in a good direction, thanks!
The one thing which I think is missing is more support for testing some of these changes in our automated testing.
In particular, devtool does have a decent test suite so we should ensure new devtool additions have tests.
You can see the devtools tests in meta/lib/oeqa/selftest/cases/devtool.py and run them with a command like "oe-selftest -r devtool -j 3" for example.
Cheers,
Richard
-- Alex Kiernan
-- Alex Kiernan
-- Alex Kiernan
-- Alex Kiernan
|
|
Just run this up locally and rebuilt our world - looks good to me. On Mon, Mar 27, 2023 at 11:13 PM Alexander Kanavin <alex.kanavin@...> wrote: I think I have meanwhile resolved the 1.68 upgrade issues: https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/package-version-updates
So that leaves the hip and cool rust-in-kernel project ;-)
Alex
On Mon, 27 Mar 2023 at 21:20, Frédéric Martinsons <frederic.martinsons@...> wrote:
Thank you alex and alexender ;)
I'll take a look at this as soon as possible and and tell you in a dedicated thread if I'm making progress. But first, I'll work for the devtool test that has been mentioned first.
Have a good evening (or day, depending on your timezone)
Le lun. 27 mars 2023, 21:00, Alexander Kanavin <alex.kanavin@...> a écrit :
For the kernel modules you could start by replicating an out-of-yocto kernel build as shown here: https://lwn.net/Articles/910762/
Alex
On Mon, 27 Mar 2023 at 20:52, Alex Kiernan <alex.kiernan@...> wrote:
IIRC the cross upgrade just works, its the target build which explodes:
https://github.com/akiernan/openembedded-core
On Mon, Mar 27, 2023 at 7:40 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
Ok great, I'm willing to know more about the bootstrap of a rust toolchain, I think I can start by just upgrading my poky master to rust 1.68 and see what it spills out when I compile the hello world
On the other hand, for enabling rust kernel modules in linux-yocto-dev, I don't know where to start (full disclosure : I have no skills about kernel and kernel module developments)
Le lun. 27 mars 2023, 20:30, Alex Kiernan <alex.kiernan@...> a écrit :
Updating the rust version is pretty much nothing to do with your rust knowledge and way more about digging into how the bootstrap process hangs together... whilst I have an awesome rustacean working for me, I don't think I've ever had to drag him into helping with an upgrade.
I wish I could say I'd spent the last few weeks figuring out why the upgrade broke, but I've been buried down the bottom of an ESP-IDF application...
Alex
On Mon, Mar 27, 2023 at 7:08 PM Frédéric Martinsons <frederic.martinsons@...> wrote:
I'll look at this but I'm not sure if I can help since I'm a beginner (enthusiastic but still)
Le lun. 27 mars 2023, 19:19, Alexander Kanavin <alex.kanavin@...> a écrit :
If you'd like to do more here's off the top of my head:
- enable rust kernel modules in linux-yocto-dev
- help Alex Kiernan with update 1.67 -> 1.68; we need as many people as possible capable of updating the rust toolchain. It's often not trivial: https://lists.openembedded.org/g/openembedded-core/message/178272
Alex
On Mon, 27 Mar 2023 at 17:01, Frédéric Martinsons <frederic.martinsons@...> wrote:
Ah!
Alright, I'll try to setup a devtool test which demonstrate the usage of git subpath with the zvariant. I'll then issue a V4 series which reintroduce the zvariant recipe in meta-selftest and the unit test on it.
I must admit I felt in love for rust since the beginning of the year and considering that I use yocto on a daily basis, I'll do everything I can to extend the support of developing rust for embedded devices.
Thank you all for the advices.
Le lun. 27 mars 2023, 16:25, Alexander Kanavin <alex.kanavin@...> a écrit :
So if devtool tests would operate on zvariant recipe, then the recipe can simply go into meta-selftest after all :)
Alex
On Mon, 27 Mar 2023 at 16:20, Richard Purdie <richard.purdie@...> wrote:
On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
From: Frederic Martinsons <frederic.martinsons@...>
This series brings the support of local git repository inside a cargo based recipe.
It also enable devtool capacity on it and provide a real crate example recipe to show how things are done.
The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
xcb-proto: Fix install conflict when enable multilib. (2023-03-23 22:38:41 +0000)
are available in the Git repository at:
https://gitlab.com/fmartinsons/openembedded-core cargo-extend-support-git-and-devtool
Alex Kiernan (1): cargo_common.bbclass: Support local github repos
Frederic Martinsons (4): cargo_common.bbclass: add support of user in url for patch rust-example: provide a recipe for zvariant devtool: add support for multiple git url inside a cargo based recipe patch: support of git patches when the source uri contained subpath param The various rust/cargo/crate patches look like they're heading in a good direction, thanks!
The one thing which I think is missing is more support for testing some of these changes in our automated testing.
In particular, devtool does have a decent test suite so we should ensure new devtool additions have tests.
You can see the devtools tests in meta/lib/oeqa/selftest/cases/devtool.py and run them with a command like "oe-selftest -r devtool -j 3" for example.
Cheers,
Richard
-- Alex Kiernan
-- Alex Kiernan
-- Alex Kiernan
|
|