Jarkko Sakkinen
Posts
4330Following
313Followers
444Entrepreneur at Siltakatu Solutions Oy
OpenPGP: 3AB05486C7752FE1
@TalesFromTheArmchair Not critique for cargo per se because in order to criticize one show the better way (or actually "show the code") but somehow in the "non-generic case" cargo can be a bitch.
One example is custom targets: there should be really within a project directory a directory where they could be deployed and all the tools would automatically discover them. Then one could just use them by name.
I was so sure that I just don't know how to make that happen but I'd presume that it is not possible reflecting e.g. this tutorial:
https://security.googleblog.com/2024/09/deploying-rust-in-existing-firmware.html
I trust that Google would know the way if that would exist.
One example is custom targets: there should be really within a project directory a directory where they could be deployed and all the tools would automatically discover them. Then one could just use them by name.
I was so sure that I just don't know how to make that happen but I'd presume that it is not possible reflecting e.g. this tutorial:
https://security.googleblog.com/2024/09/deploying-rust-in-existing-firmware.html
I trust that Google would know the way if that would exist.
1
0
0
Jarkko Sakkinen
jarkko
@TalesFromTheArmchair Thanks I honestly do appreciate your comment! Anything is really worth of a shot by now ;-)
As per Windows I learned the basics of how to debug NT kernel and now I should be able to start capture the environment of every cargo process launched:
https://social.kernel.org/notice/AqZds7vXTuTxSm2gds
I.e. build from command-line within the directory where rust-toolchain.toml and Cargo.toml reside but otherwise with same arguments as in build.rs and then do the build.rs build. Finally "subtract the sets".
What you're doing is an interesting idea, I will definitely give it a shot. Also wonder does the position of current_dir() call matter (I had it before arg() calls)....
As per Windows I learned the basics of how to debug NT kernel and now I should be able to start capture the environment of every cargo process launched:
https://social.kernel.org/notice/AqZds7vXTuTxSm2gds
I.e. build from command-line within the directory where rust-toolchain.toml and Cargo.toml reside but otherwise with same arguments as in build.rs and then do the build.rs build. Finally "subtract the sets".
What you're doing is an interesting idea, I will definitely give it a shot. Also wonder does the position of current_dir() call matter (I had it before arg() calls)....
1
0
0
Jarkko Sakkinen
jarkko
Pre-order without even reading the sample chapter:
https://nostarch.com/art-arm-assembly-volume-1
I would pay 200 for this one TBH even.
#arm #assembly #nostarch
https://nostarch.com/art-arm-assembly-volume-1
I would pay 200 for this one TBH even.
#arm #assembly #nostarch
0
0
2
Jarkko Sakkinen
jarkko
Edited 2 months ago
I just mastered Windows kernel debugging and learned how to dig globally all environment data from EPROCESS globally in the system using WinDbg :-)
It can side-effect free (except slowing down) to intervene process creation of NT kernel. I'll post the script as I test it more.
Victory in debugging after two weeks. Now I have at least proper weapons to nail the build issue in PolkaVM guest programs.
The most important skill to write e.g. Windows drivers for what is worth but also do global system tracing.
I tried all other methods but they all suck in some way.
As much I dislike Windows I have to admit that this brings me weird satisfaction ;-)
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/
#windows #nt #windbg
It can side-effect free (except slowing down) to intervene process creation of NT kernel. I'll post the script as I test it more.
Victory in debugging after two weeks. Now I have at least proper weapons to nail the build issue in PolkaVM guest programs.
The most important skill to write e.g. Windows drivers for what is worth but also do global system tracing.
I tried all other methods but they all suck in some way.
As much I dislike Windows I have to admit that this brings me weird satisfaction ;-)
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/
#windows #nt #windbg
0
0
0
Jarkko Sakkinen
repeated
repeated
Alfie Kohn
alfiekohn@sciences.socialSort of like saying GoogleMaps worked well until we tried to find the Gulf of Mexico?
1
9
0
Jarkko Sakkinen
repeated
repeated
Jarkko Sakkinen
repeated
repeated
World Wide Web Consortium
w3c@w3c.socialOn International Privacy Day we invite you to check out "Privacy Principles" for the web by @tag
"Privacy is an essential part of the web. This document provides definitions for privacy and related concepts that are applicable worldwide as well as a set of privacy principles that should guide the development of the web as a trustworthy platform."
https://www.w3.org/TR/privacy-principles/
0
3
0
Related:
1.The PR in trouble: https://github.com/paritytech/polkavm/pull/240
2. NINE years old Rust bug: https://github.com/rust-lang/rust/issues/37868
I even went on sending email to Jack who reported the Rust bug, and also is author of this crate: https://docs.rs/duct/latest/duct/.
Well, he did not have off-the-shelf answer but he did say that I should probably remove env_clear(). In Linux actually removing it breaks the build and makes it behave like the Windows build.
I'm a bit pessimistic ATM ;-)
1.The PR in trouble: https://github.com/paritytech/polkavm/pull/240
2. NINE years old Rust bug: https://github.com/rust-lang/rust/issues/37868
I even went on sending email to Jack who reported the Rust bug, and also is author of this crate: https://docs.rs/duct/latest/duct/.
Well, he did not have off-the-shelf answer but he did say that I should probably remove env_clear(). In Linux actually removing it breaks the build and makes it behave like the Windows build.
I'm a bit pessimistic ATM ;-)
0
0
0
Jarkko Sakkinen
jarkko
Any known examples in open source products doing the following pattern with Rust:
1. You have a Rust crate that you compile to you compile as usual host-to-host.
2. You have a build.rs that spawns cargo to a directory with rust-toolchain.xml defining nightly target.
3. You pass options (e.g. --target) for cargo to compile for a different target than the host.
Obviously Command is used to create the process together with current_directory() to change the directory to the one with Cargo.toml and rust-toolchain.xml. It is not a sub-crate per se topologically but a disjoint crate.
In Linux and macOS this can be made to work. With Windows cargo is acting like --target etc. options did not exist at all and ignores rust-toolchain.xml.
Any ideas how to make this type of pattern work?
#rust #rustlang #cargo #windows #riscv
1. You have a Rust crate that you compile to you compile as usual host-to-host.
2. You have a build.rs that spawns cargo to a directory with rust-toolchain.xml defining nightly target.
3. You pass options (e.g. --target) for cargo to compile for a different target than the host.
Obviously Command is used to create the process together with current_directory() to change the directory to the one with Cargo.toml and rust-toolchain.xml. It is not a sub-crate per se topologically but a disjoint crate.
In Linux and macOS this can be made to work. With Windows cargo is acting like --target etc. options did not exist at all and ignores rust-toolchain.xml.
Any ideas how to make this type of pattern work?
#rust #rustlang #cargo #windows #riscv
2
0
0
Jarkko Sakkinen
repeated
repeated
pixelfed
pixelfed@mastodon.socialKickstarter Update #4: 🚀 $100K Milestone Unlocked: The Fediverse Revolution Is Unstoppable!
0
5
0
Jarkko Sakkinen
repeated
repeated
Stock market chaos as China reveals secret snake oil refinery, threatening US snake oil monopoly.
4
11
0