Skip to content

simplify dart 2.0 command line execution #31808

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

Closed
a-siva opened this issue Jan 9, 2018 · 1 comment
Closed

simplify dart 2.0 command line execution #31808

a-siva opened this issue Jan 9, 2018 · 1 comment
Assignees
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. P1 A high priority bug; for example, a single project is unusable or has many test failures

Comments

@a-siva
Copy link
Contributor

a-siva commented Jan 9, 2018

Currently we have numerous options that need to be set when invoking dart 2.0 on the command line.

  1. Need to specify platform binaries location
  2. Need to specify location of the front end snapshot

Would be more ideal if we

  • generated the front end snapshot as part of the sdk
  • linked in the platform binaries into the executable
  • auto located the front end snapshot from the sdk

Would also be ideal if we could generate a core snapshot of platform binaries and linked it
into the executable instead of the platform binaries. This has the issue of figuring out how
we provide the platform binaries to the front end which requires it for incremental compilations.
(the snapshot has the kernel representation of all the core libraries, maybe the interface to the
FE can be changed to allow dart to specify the platform binaries from the snapshot).

@a-siva a-siva added the area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. label Jan 9, 2018
@a-siva a-siva added this to the 2.0-alpha milestone Jan 9, 2018
@a-siva a-siva added the P1 A high priority bug; for example, a single project is unusable or has many test failures label Jan 9, 2018
@a-siva
Copy link
Contributor Author

a-siva commented Feb 7, 2018

We have gotten rid of the requirement to specify the following options in order to run in 2.0 mode, we are down to being able to do 'dart --preview_dart_2 myapp.dart' to be able to run in 2.0 mode.

@a-siva a-siva closed this as completed Feb 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Development

No branches or pull requests

2 participants