summary refs log tree commit diff
path: root/src/librustpkg/testsuite
AgeCommit message (Collapse)AuthorLines
2013-06-29Great renaming: propagate throughout the rest of the codebaseCorey Richardson-2/+2
2013-06-25rustpkg: Begin allowing package scripts to call the default build logicTim Chevalier-6/+34
rustpkg/api.rs provides functions intended for package scripts to call. It will probably need more functionality added to it later, but this is a start. Added a test case checking that a package script can use the API. Closes #6401
2013-06-01rustc/rusti/rustpkg: Infer packages from `extern mod` directivesTim Chevalier-2/+16
This commit won't be quite as useful until I implement RUST_PATH and until we change `extern mod` to take a general string instead of an identifier (#5682 and #6407). With that said, now if you're using rustpkg and a program contains: extern mod foo; rustpkg will attempt to search for `foo`, so that you don't have to provide a -L directory explicitly. In addition, rustpkg will actually try to build and install `foo`, unless it's already installed (specifically, I tested that `extern mod extra;` would not cause it to try to find source for `extra` and compile it again). This is as per #5681. Incidentally, I changed some driver code to infer the link name from the crate link_meta attributes. If that change isn't ok, say something. Also, I changed the addl_lib_search_paths field in the session options to be an @mut ~[Path] so that it can be modified after expansion but before later phases.
2013-05-27Refactor core::run in order to address many of the issuesgareth-2/+2
mentioned in #2625. This change makes the module more oriented around Process values instead of having to deal with process ids directly. Apart from issues mentioned in #2625, other changes include: - Changing the naming to be more consistent - Process/process is now used instead of a mixture of Program/program and Process/process. - More docs/tests. Some io/scheduler related issues remain (mentioned in #2625).
2013-05-19Use assert_eq! rather than assert! where possibleCorey Richardson-1/+1
2013-05-15rustpkg: Reorganize test filesTim Chevalier-0/+0
2013-05-03add gitattributes and fix whitespace issuesDaniel Micay-2/+0
2013-04-24rustpkg: Correct directory structure in test scenariosTim Chevalier-6/+11
2013-04-22docs: Sketch out rustpkg manualTim Chevalier-21/+0
2013-04-18TidyTim Chevalier-0/+50
2013-04-17rustpkg: Add more testsTim Chevalier-0/+93
These are examples of what *should* work, and probably don't work yet.
2013-04-17rustpkg: Add a list of rustpkg commands that should passTim Chevalier-0/+35
This is a test file containing examples of commands that should succeed. When we write the test runner, we will have to figure out how to automate them.
2013-04-17rustpkg: Change this example to show how to do a custom buildTim Chevalier-0/+6
2013-04-17rustpkg: Remove bogus .rc fileTim Chevalier-25/+1
2013-04-17rustpkg: Implement clean; replace boolean result flags with fail!()Tim Chevalier-3/+6
1. Implemented the `clean` command 2. The methods implementing rustpkg commands all returned `bool`. Since most of not all of the error situations seem unrecoverable, I changed the methods to return unit (and also stubbed out several more methods that were assuming a package script existed, to be re-implemented in the future)
2013-04-17rustpkg: Add a few testsTim Chevalier-0/+161
There's no test runner for rustpkg yet; just sketching out a few basic test scenarios. pass/ contains packages that should compile successfully, whereas fail/ contains packages that should fail to build.