Hello Tim,
I'll take a look today since I already put my nose in this package for rust
ptest patch series, it was unsuccessful but I want to know more on this
package to kill two birds with one stone (hope so)
Le mer. 3 mai 2023, 19:31, Tim Orling a écrit :
> I am working on an upgrade from 39.
From: Frederic Martinsons
Below is the output of run-ptest script under qemu
root@qemux86-64:~# /usr/lib/zvariant/ptest/run-ptest
running 37 tests
test framing_offset_size::tests::framing_offset_size_bump ... ok$<2>
test owned_value::tests::from_value ... ok$<2>
test objec
From: Frederic Martinsons
The source code of bcrypt extension doesn't define any tests
but it is to show the ptest-cargo usage
Below is the updated test suite output for the recipe (cut):
PASS:
tests/test_bcrypt.py:test_invalid_params[password-$2b$04$cVWp4XaNU8a4v1uMRum2SO-513-10-Value
From: Frederic Martinsons
This brings the possibility to use this class to build and ship
unit tests of rust projects, the class also create (or modified)
standard run-ptest script to run the generated rust test suite.
It has been tested successfully with core-image-sato under qemu
for zvariant
From: Frederic Martinsons
This new class offers the possibility to build rust unit tests
(and integration tests) and find them correctly.
Due to non deterministic names of generated binaries, a custom
parsing of build result must be performed.
See https://github.com/rust-lang/cargo/issues/1924
Le jeu. 27 avr. 2023, 07:21, a écrit :
> From: Frederic Martinsons
>
> This new class offer the capbility to build rust tests and
> find them correctly.
> Due to non deterministic name of generated binaries, a custom
> parsing of build result must be performed.
> See ht
From: Frederic Martinsons
Below is the output of run-ptest script under qemu
root@qemux86-64:~# /usr/lib/zvariant/ptest/run-ptest
running 37 tests
test framing_offset_size::tests::framing_offset_size_bump ... ok$<2>
test owned_value::tests::from_value ... ok$<2>
test objec
From: Frederic Martinsons
This brings the possibility to use this class to build and ship
unit tests of rust projects, the class also create (or modified)
standard run-ptest script to run the generated rust test suite.
It has been tested successfully with core-image-sato under qemu
for zvariant
From: Frederic Martinsons
This new class offer the capbility to build rust tests and
find them correctly.
Due to non deterministic name of generated binaries, a custom
parsing of build result must be performed.
See https://github.com/rust-lang/cargo/issues/1924
All rust project will generate a
From: Frederic Martinsons
The source code of bcrypt extension doesn't define any tests
but it is to show the ptest-cargo usage
Below is the updated test suite output for the recipe (cut):
PASS:
tests/test_bcrypt.py:test_invalid_params[password-$2b$04$cVWp4XaNU8a4v1uMRum2SO-513-10-Value
Le mer. 26 avr. 2023, 23:10, Luca Ceresoli a
écrit :
> Hello Frederic,
>
> On Mon, 24 Apr 2023 15:04:10 +0200
> "Frederic Martinsons" wrote:
>
> > From: Frederic Martinsons
> >
> > This brings the possibility to use this class to build and ship
>
From: Frederic Martinsons
This brings the possibility to use this class to build and ship
unit tests of rust projects, the class also create (or modified)
standard run-ptest script to run the generated rust test suite.
It has been tested successfully with core-image-sato under qemu
for zvariant
From: Frederic Martinsons
Below is the output of run-ptest script under qemu
root@qemux86-64:~# /usr/lib/zvariant/ptest/run-ptest
running 37 tests
test framing_offset_size::tests::framing_offset_size_bump ... ok$<2>
test owned_value::tests::from_value ... ok$<2>
test objec
From: Frederic Martinsons
The source code of bcrypt extension doesn't define any tests
but it is to show the ptest-cargo usage
Below is the updated test suite output for the recipe (cut):
PASS:
tests/test_bcrypt.py:test_invalid_params[password-$2b$04$cVWp4XaNU8a4v1uMRum2SO-513-10-Value
From: Frederic Martinsons
This new class offer the capbility to build rust tests and
find them correctly.
Due to non deterministic name of generated binaries, a custom
parsing of build result must be performed.
See https://github.com/rust-lang/cargo/issues/1924
All rust project will generate a
Le lun. 24 avr. 2023, 11:53, Alexander Kanavin a
écrit :
> On Mon, 24 Apr 2023 at 11:44, Frédéric Martinsons
> wrote:
> > I looked again and python3-bcrypt is already in PTESTS_FAST , for
> zvariant , the recipe is in meta-selftest
> > so this layer is not always included, is this will be a prob
On Mon, 24 Apr 2023 at 10:20, Frederic Martinsons via lists.openembedded.org
wrote:
>
> On Mon, 24 Apr 2023 at 09:51, Alexander Kanavin
> wrote:
>
>> If you add ptests, please also add them to appropriate lists in
>> meta/conf/distro/include/ptest-packagelists.inc, so
On Mon, 24 Apr 2023 at 09:47, Alexander Kanavin
wrote:
> On Sat, 22 Apr 2023 at 18:00, Frederic Martinsons
> wrote:
>
> > +# zvariant is an indermediate product for the zbus project
> > +# and so, it provided only a static lib (rlib) which fall only
> > +# in -dev pa
you added into commit
> messages?
>
> Alex
>
Ok I will issue a V2 with the modifications asked.
> On Sat, 22 Apr 2023 at 17:59, Frederic Martinsons
> wrote:
> >
> > From: Frederic Martinsons
> >
> > This brings the possibility to use this class to build
From: Frederic Martinsons
Signed-off-by: Frederic Martinsons
---
.../recipes-extended/zvariant/zvariant_3.12.0.bb | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/meta-selftest/recipes-extended/zvariant/zvariant_3.12.0.bb
b/meta-selftest/recipes-extended
From: Frederic Martinsons
The source code of bcrypt extension doesn't define any tests
but it is to show the ptest-cargo usage
Signed-off-by: Frederic Martinsons
---
meta/recipes-devtools/python/python3-bcrypt_4.0.1.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --
From: Frederic Martinsons
This new class offer the capbility to build rust tests and
find them correctly.
Due to non deterministic name of generated binaries, a custom
parsing of build result must be performed.
See https://github.com/rust-lang/cargo/issues/1924
All rust project will generate a
From: Frederic Martinsons
This brings the possibility to use this class to build and ship
unit tests of rust projects, the class also create (or modified)
standard run-ptest script to run the generated rust test suite.
It has been tested successfully with core-image-sato under qemu
for zvariant
Le jeu. 20 avr. 2023, 17:00, Khem Raj a écrit :
> On 4/20/23 2:57 AM, Frederic Martinsons wrote:
> >
> >
> > Le jeu. 20 avr. 2023, 11:41, Richard Purdie
> > > <mailto:richard.pur...@linuxfoundation.org>> a écrit :
> >
> > On Thu, 2
Le jeu. 20 avr. 2023, 11:41, Richard Purdie <
richard.pur...@linuxfoundation.org> a écrit :
> On Thu, 2023-04-20 at 09:27 +0200, Frederic Martinsons wrote:
> > Hello,
> >
> > I would like to build and ship tests for recipes which uses cargo and
> > in the proc
can't add it to them.
>
> Alex
>
> On Thu, 20 Apr 2023 at 09:27, Frederic Martinsons
> wrote:
> >
> > Hello,
> >
> > I would like to build and ship tests for recipes which uses cargo and in
> the process, three questions arose (maybe more when I w
Hello,
I would like to build and ship tests for recipes which uses cargo and in
the process, three questions arose (maybe more when I will progress).
I would like to have your opinions on them.
1) should we ship cargo-native in ptest images or should we just build and
ship test binaries alone ?
2
I opened a dedicated ticket (
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15104) for this issue.
On Thu, 13 Apr 2023 at 13:50, Frederic Martinsons via lists.openembedded.org
wrote:
> By the way, it was way simpler to update my cargo to 1.68.2 and I confirm
> the patching still work
By the way, it was way simpler to update my cargo to 1.68.2 and I confirm
the patching still works like a charm.
On Thu, 13 Apr 2023 at 13:40, Frederic Martinsons via lists.openembedded.org
wrote:
> Hello,
>
> Since I didn't manage to make any progress on the reproducibility issue
Hello,
Since I didn't manage to make any progress on the reproducibility issue of
zvariant (https://bugzilla.yoctoproject.org/show_bug.cgi?id=15090) i
decided to try another rust project to see their reproducibility state.
I went with zbus (https://github.com/zeenix/zbus) which use zvariant
(beca
Le mar. 11 avr. 2023, 18:41, Richard Purdie <
richard.pur...@linuxfoundation.org> a écrit :
> On Tue, 2023-04-11 at 17:27 +0200, Frédéric Martinsons wrote:
> > Hello with the patch below:
> >
> > --- a/meta/lib/oeqa/selftest/cases/reproducible.py
> > +++ b/meta/lib/oeqa/selftest/cases/reproducible
dmit I'm surprised , I would have waited for some random diff.
I'll continue my investigation but if this rang a bell to someone here,
feel free to tell (this does
seem strange to me).
On Mon, 10 Apr 2023 at 18:38, Frederic Martinsons via lists.openembedded.org
wrote:
>
>
ed.
>
> Alternatively, you can set up two separate build directories, and
> avoid selftest altogether for investigating and fixing the issue.
>
> Alex
>
> On Fri, 7 Apr 2023 at 17:21, Frederic Martinsons
> wrote:
> >
> > Hello,
> >
> > I plan to work
On Mon, 10 Apr 2023 at 17:32, Jose Quaresma wrote:
> Hi Frederic,
>
> Frederic Martinsons escreveu no dia
> domingo, 9/04/2023 à(s) 16:05:
>
>>
>>
>> Le dim. 9 avr. 2023, 10:43, Richard Purdie <
>> richard.pur...@linuxfoundation.org> a écrit :
>&
Le dim. 9 avr. 2023, 10:43, Richard Purdie <
richard.pur...@linuxfoundation.org> a écrit :
> On Sat, 2023-04-08 at 09:56 +0200, Frederic Martinsons wrote:
> > Forget my previous question,
> >
> > I simply
> > edit https://git.openembedded.org/openembedded-core
cannot be avoided
since there are two builds and one
without any shared state.
On Fri, 7 Apr 2023 at 17:21, Frederic Martinsons via lists.openembedded.org
wrote:
> Hello,
>
> I plan to work on https://bugzilla.yoctoproject.org/show_bug.cgi?id=15090
> in the coming days.
> To show
Hello,
I plan to work on https://bugzilla.yoctoproject.org/show_bug.cgi?id=15090
in the coming days.
To show how things are tested I ran "oe-selftest -r
reproducible.ReproducibleTests.test_reproducible_builds" but even on a
strong machine, it took several hours (I waited for 6h and it is not
finis
le/dunfell-nut&id=d17f4c741c66268ce54ff89be2be9b0402c98df2
>
> On 4/6/2023 10:16 PM, Frederic Martinsons wrote:
> > Hello,
> >
> > I came across a build issue for qemu-system-native on dunfell branch
> > when using spice PACKAGECONFIG.
> > I found that the culprit is the
Hello,
I came across a build issue for qemu-system-native on dunfell branch when
using spice PACKAGECONFIG.
I found that the culprit is the CVE-2022-4144.patch introduced mid-march
and that was merged in upstream
end of november 2022:
https://gitlab.com/qemu-project/qemu/-/commit/6dbbf055148c6f1b7
Le jeu. 6 avr. 2023, 10:23, Michael Opdenacker <
michael.opdenac...@bootlin.com> a écrit :
> Hi Frederic
>
> On 05.04.23 at 21:04, Frederic Martinsons wrote:
> >
> >
> >
> > Any more Rust changes we should mention in the migration notes?
> >
On Wed, 5 Apr 2023 at 20:40, Michael Opdenacker <
michael.opdenac...@bootlin.com> wrote:
> Greetings,
>
> I copied the OE-core mailing list to get the attention of contributors.
> If you want your new features to be featured in the release and
> migration notes for 4.2, it's time to speak!
>
> Wha
Nice, glad to hear that.
Le lun. 3 avr. 2023, 15:35, Richard Purdie <
richard.pur...@linuxfoundation.org> a écrit :
> On Sat, 2023-04-01 at 17:21 +0200, Frederic Martinsons wrote:
> > Hello, I just submitted a patch inside the bitbake fetcher to display
> > all the mis
Hello, I just submitted a patch inside the bitbake fetcher to display all
the missing
checksum at once instead of only one.
For the moment, I have no better solution, let's see what bitbake folks
tell us about that.
On Fri, 31 Mar 2023 at 07:32, Frederic Martinsons via lists.openembedde
I just submit a V7 of this series with EXCLUDE_FROM_WORLD set for zvariant
and
open a dedicated bug for the reproducibility issue:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15090
On Fri, 31 Mar 2023 at 18:34, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Fri, 2023-03-31
From: Frederic Martinsons
This recipe is for showing a "real world" example of
a crate that depends on some git repositories.
Usually, this kind of crate is built within a global
workspace (here it is the zbus project) and so
doesn't need a Cargo.lock on its own.
For
From: Frederic Martinsons
A project can have multiple Cargo.lock (provides
multiple binaries for example) and each one can
depends on differenct version of the same crates.
Even within the same Cargo.lock file, it is possible
to have different version of same crates.
To avoid conflicts
From: Frederic Martinsons
This is for a specific case where:
- A recipe use a subpath on a git repo (e.g.
git://repo.git/projects;subpath=subproject)
- The recipe contains a patch to apply
- a devtool modify is used on this recipe
With these conditions, the patch cannot be applied at all
From: Frederic Martinsons
To handle url like git://git@repo/project
Signed-off-by: Frederic Martinsons
---
meta/classes-recipe/cargo_common.bbclass | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/cargo_common.bbclass
b/meta/classes-recipe
From: Frederic Martinsons
Without that, the possible git urls that are in SRC_URI of a recipe
are removed from SRC_URI during devtool process and so the
cargo_common_do_patch_paths in cargo_common.bbclass cannot
patch these packages to fetch them locally.
I use a generic type name because I
From: Alex Kiernan
Since disable network was added cargo configurations which reference git
repos fail as they attempt to fetch across the network as part of
do_compile, even if EXTRA_OECARGO_PATHS to add them as part of `paths`
is used, as this is documented as only working for packages which ex
From: Frederic Martinsons
This series brings the support of local git repository inside
a cargo based recipe.
It also enables devtool capacity to such a recipe along with
an example of recipe and a new selftest case.
The following changes since commit 491d1259e2f78233f17bb901cdac5b9aa520
Ok thanks.
Le ven. 31 mars 2023, 17:55, Alexander Kanavin a
écrit :
> You need to set up two identical builds in different build directories
> and verify that what gets installed and packaged is identical (in this
> case it's not). The most common problem is build paths leaking into
> the binari
Ok I'll take a look at this next week. But I don't know anything about
reproductability build so if you have any info that can point me to the
right direction, I'll be glad to read it.
Le ven. 31 mars 2023, 15:50, Alexander Kanavin a
écrit :
> On Fri, 31 Mar 2023 at 15:26, Richard Purdie
> wrot
From: Frederic Martinsons
Without that, the possible git urls that are in SRC_URI of a recipe
are removed from SRC_URI during devtool process and so the
cargo_common_do_patch_paths in cargo_common.bbclass cannot
patch these packages to fetch them locally.
I use a generic type name because I
From: Frederic Martinsons
This recipe is for showing a "real world" example of
a crate that depends on some git repositories.
Usually, this kind of crate is built within a global
workspace (here it is the zbus project) and so
doesn't need a Cargo.lock on its own.
For
From: Frederic Martinsons
A project can have multiple Cargo.lock (provides
multiple binaries for example) and each one can
depends on differenct version of the same crates.
Even within the same Cargo.lock file, it is possible
to have different version of same crates.
To avoid conflicts
From: Frederic Martinsons
This is for a specific case where:
- A recipe use a subpath on a git repo (e.g.
git://repo.git/projects;subpath=subproject)
- The recipe contains a patch to apply
- a devtool modify is used on this recipe
With these conditions, the patch cannot be applied at all
From: Frederic Martinsons
To handle url like git://git@repo/project
Signed-off-by: Frederic Martinsons
---
meta/classes-recipe/cargo_common.bbclass | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/cargo_common.bbclass
b/meta/classes-recipe
From: Alex Kiernan
Since disable network was added cargo configurations which reference git
repos fail as they attempt to fetch across the network as part of
do_compile, even if EXTRA_OECARGO_PATHS to add them as part of `paths`
is used, as this is documented as only working for packages which ex
From: Frederic Martinsons
This series brings the support of local git repository inside
a cargo based recipe.
It also enables devtool capacity to such a recipe along with
an example of recipe and a new selftest case.
The following changes since commit c3fe173d5196506d89aa464ba56aabcf581a60db
>>> recipes, but isn't there some valid use-case for multiple Cargo.locks?
>>>>> I assume Alex in original implementation didn't use the os.walk just
>>>>> to make it more complicated :).
>>>>>
>>>>> And FWIW when trying t
:
>> SRC_URI[Inflector.sha256sum] =
>> "fe438c63458706e03479442743baae6c88256498e6431708f6dfc520a26515d3"
>> ERROR: solana-keygen-1.14.5-r0 do_fetch: Bitbake Fetcher Error:
>> NoChecksumError('Missing SRC_URI checksum', '
>> https://crates
etch enforces checksums to be
> used? Or am I just missing some of the pending changes or just using it
> incorrectly?
>
>
> On Thu, Mar 30, 2023 at 6:34 PM Alex Kiernan
> wrote:
>
>> On Thu, Mar 30, 2023 at 4:45 PM wrote:
>> >
>> > From: Frederic
Nevermind, I'll submit a new v6 series tomorrow.
Your comment is totally accurate and follow the PEP20 which I should follow
too ("readability counts" and "explicit is better than implicit" at most )
Le jeu. 30 mars 2023, 19:10, Frederic Martinsons via lists.openembedded
> > From: Frederic Martinsons
> >
> > There is no need to do such things, Cargo.lock file
> > has to be at the root of CARGO_LOCK_SRC_DIR.
> > This avoid finding other possible Cargo.lock that
> > would be in subdir (for example if a patch is applied
> > on the r
From: Frederic Martinsons
There is no need to do such things, Cargo.lock file
has to be at the root of CARGO_LOCK_SRC_DIR.
This avoid finding other possible Cargo.lock that
would be in subdir (for example if a patch is applied
on the recipe, we can have .pc subdir in S and a Cargo.lock
can be
From: Frederic Martinsons
This recipe is for showing a "real world" example of
a crate that depends on some git repositories.
Usually, this kind of crate is built within a global
workspace (here it is the zbus project) and so
doesn't need a Cargo.lock on its own.
For
From: Frederic Martinsons
This is for a specific case where:
- A recipe use a subpath on a git repo (e.g.
git://repo.git/projects;subpath=subproject)
- The recipe contains a patch to apply
- a devtool modify is used on this recipe
With these conditions, the patch cannot be applied at all
From: Frederic Martinsons
Without that, the possible git urls that are in SRC_URI of a recipe
are removed from SRC_URI during devtool process and so the
cargo_common_do_patch_paths in cargo_common.bbclass cannot
patch these packages to fetch them locally.
I use a generic type name because I
From: Frederic Martinsons
To handle url like git://git@repo/project
Signed-off-by: Frederic Martinsons
---
meta/classes-recipe/cargo_common.bbclass | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/cargo_common.bbclass
b/meta/classes-recipe
From: Frederic Martinsons
This series brings the support of local git repository inside
a cargo based recipe.
It also enables devtool capacity to such a recipe along with
an example of recipe and a new selftest case.
The following changes since commit c3fe173d5196506d89aa464ba56aabcf581a60db
From: Alex Kiernan
Since disable network was added cargo configurations which reference git
repos fail as they attempt to fetch across the network as part of
do_compile, even if EXTRA_OECARGO_PATHS to add them as part of `paths`
is used, as this is documented as only working for packages which ex
Ah, when trying to update the checksum, I encounter an issue in
do_update_crates (specific to the zvariant recipe structure), I'll add
another patch for that.
Le jeu. 30 mars 2023, 14:26, Frederic Martinsons via lists.openembedded.org
a écrit :
> Ok, I'll do this rebase in the
Ok, I'll do this rebase in the coming hours.
On Thu, 30 Mar 2023 at 13:35, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Thu, 2023-03-30 at 11:47 +0200, Frederic Martinsons wrote:
> > What version of bitbake you had pulled ?
> > Because "man
From: Frederic Martinsons
This recipe is for showing a "real world" example of
a crate that depends on some git repositories.
Usually, this kind of crate is built within a global
workspace (here it is the zbus project) and so
doesn't need a Cargo.lock on its own.
For
From: Frederic Martinsons
This is for a specific case where:
- A recipe use a subpath on a git repo (e.g.
git://repo.git/projects;subpath=subproject)
- The recipe contains a patch to apply
- a devtool modify is used on this recipe
With these conditions, the patch cannot be applied at all
From: Frederic Martinsons
Without that, the possible git urls that are in SRC_URI of a recipe
are removed from SRC_URI during devtool process and so the
cargo_common_do_patch_paths in cargo_common.bbclass cannot
patch these packages to fetch them locally.
I use a generic type name because I
From: Frederic Martinsons
To handle url like git://git@repo/project
Signed-off-by: Frederic Martinsons
---
meta/classes-recipe/cargo_common.bbclass | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/cargo_common.bbclass
b/meta/classes-recipe
From: Frederic Martinsons
This series brings the support of local git repository inside
a cargo based recipe.
It also enables devtool capacity to such a recipe along with
an example of recipe and a new selftest case.
The following changes since commit fd70a564d6946fa460638dd04ce2daecf4566cf3
From: Alex Kiernan
Since disable network was added cargo configurations which reference git
repos fail as they attempt to fetch across the network as part of
do_compile, even if EXTRA_OECARGO_PATHS to add them as part of `paths`
is used, as this is documented as only working for packages which ex
Thanks, after having "fixed" /tmp, I managed to play
test_devtool_modify_git successfully.
Le mar. 28 mars 2023, 22:04, Alexander Kanavin a
écrit :
> Not devtool's fault. The selftest is written so that devtool is
> instructed to use /tmp/... to extract sources, and not a workspace in
> a build:
Oh my, your assumption is surely correct, my build host /tmp is mounted
with noexec so no chance to execute
anything there:
[ (8) ] jenkins@cibuilder2:~$ mount | grep "/tmp"
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noexec,noatime,inode64)
Tomorrow, I'll try with another machine (or talk to the a
I rebuilt a poky master from scratch on another machine (Ubuntu 22.04 , 16
Xeon, 124 Gb RAM), it took
2h30mn to finish (note that rust-llvm-native and llvm-native both took
around 1h each to be built).
I have two questions for my curiosity:
- why rust things (cargo-native, librsvg) are the la
Note that I managed to build libtirpc-native and shadow-native with bitbake
(and the same setup).
I currently try the build on another machine and under /home.
I'll tell you the results soon
Le mar. 28 mars 2023, 15:13, Richard Purdie <
richard.pur...@linuxfoundation.org> a écrit :
> On Tue, 20
Ah sorry, I take it back, only test_devtool_modify passed, I still
have errors on test_devtool_modify_git:
NOTE: recipe psplash-0.1+git999-r0: task do_configure: Started
ERROR: psplash-0.1+git999-r0 do_configure: no configure script found at
../../../../../../../../../../../../tmp/devtoolqantpyns7
I just finished a pristine build of core-image-sato on poky master,
and set up SSTATE_DIR in my local.conf.
Tests are now ok, I can start to write some now.
If anyone is interested , please find attached the full log of the two
first failures.
On Tue, 28 Mar 2023 at 14:28, Richard Purdie <
richar
Hello,
in the course of building tests around this patch:
https://patchwork.yoctoproject.org/project/oe-core/patch/855931994ea68c0691d0a67ce2ccad947e77229f.1679904677.git.frederic.martins...@gmail.com/
I tried to run oe-selftest with the current poky master
(e3afe166940686b05626c3298bc4369296b7d8
;> >> > 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 zvarian
g rust for embedded devices.
> >> >
> >> > Thank you all for the advices.
> >> >
> >> > Le lun. 27 mars 2023, 16:25, Alexander Kanavin <
> alex.kana...@gmail.com> a écrit :
> >> >>
> >> >> So if
the advices.
> >
> > Le lun. 27 mars 2023, 16:25, Alexander Kanavin
> a écrit :
> >>
> >> So if devtool tests would operate on zvariant recipe, then the recipe
> >> can simply go into meta-selftest after all :)
> >>
> >> Alex
> &g
n the recipe
> can simply go into meta-selftest after all :)
>
> Alex
>
> On Mon, 27 Mar 2023 at 16:20, Richard Purdie
> wrote:
> >
> > On Sat, 2023-03-25 at 10:00 +0100, Frederic Martinsons wrote:
> > > From: Frederic Martinsons
> > >
> > >
> On Mon, 27 Mar 2023 at 10:58, Peter Bergin wrote:
> >
> >
> > On 2023-03-26 16:56, Frederic Martinsons wrote:
> > > From: Frederic Martinsons
> > >
> > > This recipe is for showing a "real world" example of
> > > a crate
From: Frederic Martinsons
This is for a specific case where:
- A recipe use a subpath on a git repo (e.g.
git://repo.git/projects;subpath=subproject)
- The recipe contains a patch to apply
- a devtool modify is used on this recipe
With these conditions, the patch cannot be applied at all
From: Frederic Martinsons
Without that, the possible git urls that are in SRC_URI of a recipe
are removed from SRC_URI during devtool process and so the
cargo_common_do_patch_paths in cargo_common.bbclass cannot
patch these packages to fetch them locally.
I use a generic type name because I
From: Frederic Martinsons
To handle url like git://git@repo/project
Signed-off-by: Frederic Martinsons
---
meta/classes-recipe/cargo_common.bbclass | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/cargo_common.bbclass
b/meta/classes-recipe
From: Frederic Martinsons
This series brings the support of local git repository inside
a cargo based recipe.
It also enables devtool capacity on it.
The following changes since commit 4876189dd2ae5a04a296b11b537b9f613159c6bf:
xcb-proto: Fix install conflict when enable multilib. (2023-03
From: Alex Kiernan
Since disable network was added cargo configurations which reference git
repos fail as they attempt to fetch across the network as part of
do_compile, even if EXTRA_OECARGO_PATHS to add them as part of `paths`
is used, as this is documented as only working for packages which ex
07:15, Frédéric Martinsons <
> frederic.martins...@gmail.com> wrote:
> >>
> >> Ah, good idea, I'll try that and provide a V2 of this series if it fits.
> >>
> >> On Sat, 25 Mar 2023 at 20:02, Alexander Kanavin
> wrote:
> >>&g
Sat, 25 Mar 2023 at 20:02, Alexander Kanavin
> wrote:
>
>> On Sat, 25 Mar 2023 at 10:01, Frederic Martinsons
>> wrote:
>> > @@ -72,6 +73,8 @@ python () {
>> > url_data.type == 'npmsw' or url_data.type ==
>> &
From: Frederic Martinsons
This recipe is for showing a "real world" example of
a crate that depends on some git repositories.
Usually, this kind of crate is built within a global
workspace (here it is the zbus project) and so
doesn't need a Cargo.lock on its own.
For
101 - 200 of 240 matches
Mail list logo
