-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add all packages #4
base: empty_repository
Are you sure you want to change the base?
Conversation
This reverts commit 5528cc4.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really cool stuff!
You are running the tests for different platforms, might want to also test the lower SDK bounds, and check if pub downgrade
breaks anything.
@@ -0,0 +1,39 @@ | |||
<!-- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An actual readme would be nice ;)
} | ||
|
||
if (!buildConfig.dryRun) { | ||
await toolchain.toolchain.rustup.runCommand( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For my use case specifically, I probably want to pass some more arguments to cargo
, see https://github.com/dart-lang/i18n/blob/main/.github/workflows/intl4x_artifacts.yml. Maybe adding a field List<String> additionalFlags
to the RustBuilder
might help? I don't know if the order of args matters - that would make things more complicated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extra cargo arguments are missing. This slipped my mind. I couldn't even port super_native_extensions (the primary use-case for us right now) to native assets without this.
No description provided.