about summary refs log tree commit diff
path: root/src/rt/rust_kernel.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2013-07-20 02:16:41 -0700
committerbors <bors@rust-lang.org>2013-07-20 02:16:41 -0700
commitfdbd56ca38c4a58377056c63e0b03b0d4e131f2c (patch)
tree7c6cad3f140361d7939bc3d45c8c4ff6a14aefcb /src/rt/rust_kernel.cpp
parent098709aa638bb29998b5e6f2700997b13c2c6712 (diff)
parente39ea2a5c880b252abbf37dade7a9b7ce7b2cb40 (diff)
downloadrust-fdbd56ca38c4a58377056c63e0b03b0d4e131f2c.tar.gz
rust-fdbd56ca38c4a58377056c63e0b03b0d4e131f2c.zip
auto merge of #7419 : catamorphism/rust/default-package, r=graydon
r? @brson `rustpkg build`, if executed in a package source directory inside
a workspace, will now build that package. By "inside a workspace"
I mean that the parent directory has to be called `src`, and rustpkg
will create a `build` directory in .. if there isn't already one.

Same goes for `rustpkg install` and `rustpkg clean`.

For the time being, `rustpkg build` (etc.) will still error out if
you run it inside a directory whose parent isn't called `src`.
I'm not sure whether or not it's desirable to have it do something
in a non-workspace directory.
Diffstat (limited to 'src/rt/rust_kernel.cpp')
0 files changed, 0 insertions, 0 deletions