Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
auto merge of #10422 : alexcrichton/rust/explicit-crate-map, r=pcwalton
As we start to move runtime components into the crate map, it's becoming harder and harder to start the runtime from a C function as rust is embedded in another application. Right now if you compile a rust crate as a dynamic library which is then linked to another application, when using std::rt::start there are no I/O local services, even though rustuv was linked against and requested. The reason for this is that there is no top level crate map available specifying where to find libuv I/O. This option is not meant to be used regularly, but rather whenever compiling a final library crate and linking it into another application. This lifts the requirement that to get a crate map you must have the final destination be an executable.
- Loading branch information