librustc cannot be used as a library?

[killerswan]

When running my program:

meow $ make run_loop
./bin/testloop ./src/demo.rs --test
<<<< building tests >>>>
error: multiple input filenames provided
task 'rustc' failed at 'explicit failure', /Users/kevin/code/rust/src/librustc/driver/driver.rs:1054
task '<main>' failed at 'explicit failure', /Users/kevin/code/rust/src/librustc/lib.rs:398
make: *** [run_loop] Error 101

The "multiple input filenames provided" error is due to using the same arguments with librustc::main_args as I was using with the rustc executable. :(

https://github.com/killerswan/meow/compare/librustc#diff-7df04b77326b8a50f8284f3ac22257e3L119

That's pretty weird considering that the function I'm using is called like so inside rustc:

pub fn main() {
    std::os::set_exit_status(main_args(std::os::args()));
}

[huonw]

std::os::args() includes the current executable name, i.e. ./foo bar baz gives args() == ~[~"./foo", ~"bar", ~"baz"], so this is as if you were calling rustc like rustc ./bin/testloop ./src/demo.rs --test. Try removing/slicing out the first element of args().

(Closing, feel free to reopen if the above doesn't fix it.)

[huonw]

Wait, I misinterpreted your code sample; sorry.

[killerswan]

This is a cleaner looking diff: killerswan/meow@master...librustc#diff-7df04b77326b8a50f8284f3ac22257e3R134

[alexcrichton]

In that last diff you posted, args[0] must be the executable name, not the -o flag (hence you have two inputs on the command line), so closing as working-as-intended.

[killerswan]

Ahhh, so it is the opposite of what @huonw was thinking at first glance!