f00b146481
This change introduces a new informational message category to the overall diagnostics infrastructure, and then wires up the resource provider plugins stdout/stderr streams to it. In particular, a write to stdout implies an informational message, whereas a write to stderr implies an error. This is just a very simple and convenient way for plugins to provide progress reporting; eventually we may need something more complex, due to parallel evaluation of resource graphs, however I hope we don't have to deviate too much from this. |
||
---|---|---|
.. | ||
aws | ||
mu | ||
mujs | ||
mux | ||
README.md |
mu/lib
This directory contains the various MuPackage libraries that Mu programs may depend upon. The Mu standard library
(under mu/
) is special in that every Mu program will ultimately use it directly or indirectly to create resources.
Note that these are written in the Mu subsets of the languages and therefore cannot perform I/O, etc.
Eventually these packages will be published like any other NPM MuPackage. For now, they are consumed only in a development capacity, and so there are some manual steps required to prepare a development workspace.
For each library <lib>
you wish to use, in dependency order:
cd <lib>
yarn install
- For each dependency
<dep>
:yarn link dep
yarn build
yarn link
And then from within each MuPackage's directory that will consume said libraries, for each such library <lib>
:
yarn link <lib>
For example, let's say we want to use the Mu standard library and the AWS library from a MuPackage /dev/mypackage
:
- First,
cd $GOPATH/src/github.com/marapongo/mu/lib/mu
:yarn install
yarn build
yarn link
- Next,
cd $GOPATH/src/github.com/marapongo/mu/lib
:yarn install
yarn link mu
yarn build
yarn link
- Finally,
cd /dev/mypackage
:yarn link mu
yarn link @mu/aws
- Now we are ready to go working on
mypackage
; references tomu
and@mu/aws
will be resolved correctly.