commit | 915f003c8eaf15f4a03fede7e971abf90b18b4a0 | [log] [tgz] |
---|---|---|
author | Todd Wang <toddw@google.com> | Tue Mar 15 16:33:55 2016 -0700 |
committer | Todd Wang <toddw@google.com> | Wed Mar 16 20:09:21 2016 +0000 |
tree | fb9243df1dded7a1c042440c84b5b300268ef44d | |
parent | fa37499dba6fea1128f61972c0d92bf3cc19e96f [diff] |
vdl: Always use the built-in vdlroot standard packages. Before this change, we had vdlroot standard packages built-in to the vdl binary. This support was used in the java/gradle world, but wasn't used elsewhere. We'd simply forgotten to complete the migration. We also had some technical issues; e.g. we'd need to move the built-in vdlroot from the vdl binary into the vdl/build package, so that all users would be able to call build.TransitivePackages, even if they didn't have the vdl sources. But that would be messy, since the previous compiled-in tarball approach required that we untar into a temp directory, and cleanup is painful. After this change, we use go-bindata to archive the vdlroot packages into the vdl/build package, which we can access directly from memory. This sidesteps the tmpdir cleanup issue, and is also generally cleaner. As a result we can also remove the long-standing hack of falling back on JIRI_ROOT to find the sources if VDLROOT isn't set. In the new world, the vdl compiler will use the built-in vdlroot sources by default. You can override this by setting VDLROOT; that's still needed in order for us to be able to update the vdlroot sources. This is better behavior. We shouldn't have required that the vdlroot sources were available for end users to use the vdl tool in the first place; that was meant as a temporary hack. Fixes v.io/i/1228 Change-Id: If71e1663221d508992030a032737c6ef138ff72c
This repository contains a reference implementation of the Vanadium APIs.
Unlike the APIs in https://github.com/vanadium/go.v23, which promises to provide backward compatibility this repository makes no such promises.