Pub transformer that compiles .asm files to .exe.
I created this for use with my experiment WinDart, to have Dart files in my
compiled to MASM Assembly, and then assembled and linked to .exe files.
You will need MASM32 installed, and it to be installed to C:\masm32. Alternatively, you can pass an
masm_path in the configuration,
and ML and LINK will be run from that directory.
dependencies: masm: ^1.0.0-dev needs
This library is a transformer, and supports some options.
transformers: - windart - masm
true, then the executable will be run on completion.
run: false ml: c: true coff: true Cp: true link: SUBSYTEM: CONSOLE LIBPATH: "C:\\masm32\\lib"
Add this to your package's pubspec.yaml file:
dependencies: masm: ^1.0.0-dev+1
You can install packages from the command line:
$ pub get
Alternatively, your editor might support
Check the docs for your editor to learn more.
Now in your Dart code, you can use:
|1.0.0-dev+1||Jun 29, 2016|
|1.0.0-dev||Jun 29, 2016|
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
The package version is not analyzed, because it does not support Dart 2. Until this is resolved, the package will receive a health and maintenance score of 0.
Fix dependencies in
pub upgrade failed with the following output:
ERR: The current Dart SDK version is 2.1.0. Because masm depends on barback >=0.6.2 which requires SDK version >=0.6.2 <2.0.0 or >=2.0.0-dev.17.0 <2.0.0, version solving failed.
dartfmt to format
Add SDK constraint in
pubspec.yaml. (-50 points)
For information about setting SDK constraint, please see https://www.dartlang.org/tools/pub/pubspec#sdk-constraints.
Fix platform conflicts. (-20 points)
Error(s) prevent platform classification:
Fix dependencies in
dartdoc failed. (-10 points)
dartdoc runs without any issues.
Package is too old. (-100 points)
The package was released more than two years ago.
CHANGELOG.md. (-20 points)
Changelog entries help clients to follow the progress in your code.
The description is too short. (-20 points)
Add more detail about the package, what it does and what is its target use case. Try to write at least 60 characters.
Maintain an example. (-10 points)
Create a short demo in the
example/ directory to show how to use this package. Common file name patterns include:
example.dart or you could also use
Package is pre-release. (-5 points)
Pre-release versions should be used with caution, their API may change in breaking ways.