Eric Seidel 8ad5f14611 Currently we use package: to mean "/gen", which is not at all how
Dart actually expects package: to work.  This CL makes package:foo
map to /packages/foo, similar to how Dartium or bin/dart would expect.

This also means overlaying the /gen directory over the actual package
outputs (as consumers of an SDK would expect) as well as adding
an additional /lib indirection for the actual package source as
the Dart pub tool will expect.

This is far from perfect, but it unlocks us actually producing a
sky SDK.

I expect there may be some fallout from this change as I'm sure I
missed some package: uses.  We also don't have a general solution
for all /foo/bar/baz includes which randomly included parts
of mojo's source directory.  Those will need to be updated to use
a package: and deploy_sdk.py taught how to build a package for them.

R=abarth@chromium.org

Review URL: https://codereview.chromium.org/990493002
2015-03-13 16:58:53 -07:00
..

sky_server instructions
#######################

Building locally:
1. cd sky/tools/skygo
2. go build sky_server.go

Testing locally:
1. Build as per the above steps
2. Run test_sky --path-to-server /absolute/path/to/sky/tools/skygo/sky_server

Uploading the locally built server
1. cd sky/tools/skygo
2. upload_to_google_storage.py --bucket mojo sky_server

upload_to_google_storage.py is in depot_tools. It will overwrite
sky_server.sha1. Include that change in your code review.

sky_server was last built using go version go1.3 linux/amd64.