summary refs log tree commit diff
path: root/src/bootstrap/config.toml.example
AgeCommit message (Collapse)AuthorLines
2016-10-31detect gdb version & rust support in compiletestTim Neumann-0/+3
2016-10-19Enable line number debuginfo in releasesAlex Crichton-0/+3
This commit enables by default passing the `-C debuginfo=1` argument to the compiler for the stable, beta, and nightly release channels. A new configure option was also added, `--enable-debuginfo-lines`, to enable this behavior in developer builds as well. Closes #36452
2016-10-14Add AppVeyor configuration to the repoAlex Crichton-0/+3
We hope to move to AppVeyor in the near future off of Buildbot + EC2. This adds an `appveyor.yml` configuration file which is ready to run builds on the auto branch. This is also accompanied with a few minor fixes to the build system and such to accomodate AppVeyor. The intention is that we're not switching over to AppVeyor entirely just yet, but rather we'll watch the builds for a week or so. If everything checks out then we'll start gating on AppVeyor instead of Buildbot!
2016-09-07Auto merge of #36292 - japaric:musl-root, r=alexcrichtonbors-4/+6
rustbuild: per target musl-root config.toml now accepts a target.$TARGET.musl-root key that lets you override the "build" musl-root value, which is set via the --musl-root flag or via the build.musl-root key. With this change, it's now possible to compile std for several musl targets at once. Here's are the sample commands to do such thing: ``` $ configure \ --enable-rustbuild \ --target=x86_64-unknown-linux-musl,arm-unknown-linux-musleabi \ --musl-root=/musl/x86_64-unknown-linux-musl/ $ edit config.toml && tail config.toml [target.arm-unknown-linux-musleabi] musl-root = "/x-tools/arm-unknown-linux-musleabi/arm-unknown-linux-musleabi/sysroot/usr" $ make ``` r? @alexcrichton With this we should be able to start producing releases of std for arm musl targets
2016-09-06add utility musl_root method, update config.toml.exampleJorge Aparicio-4/+6
2016-09-04Rollup merge of #36234 - durka:disable-codegen-config, r=alexcrichtonManish Goregaokar-0/+4
rustbuild: add config.toml option to disable codegen tests Fixes #36232. I think it worked? Here's a build log where I tried to bootstrap, it crashed, then I added the setting to config.toml and it continued: https://gist.github.com/durka/cbf97cf04b8e065f1a2cfda4c1b6bf95 r? @alexcrichton
2016-09-03rustbuild: add config.toml option to disable codegen testsAlex Burka-0/+4
2016-09-03change wordingAlex Burka-1/+2
2016-09-02indicate where to copy config.toml.exampleAlex Burka-0/+2
2016-07-26rustbuild: make backtraces (RUST_BACKTRACE) optionalJorge Aparicio-0/+3
but keep them enabled by default to maintain the status quo. When disabled shaves ~56KB off every x86_64-unknown-linux-gnu binary. To disable backtraces you have to use a config.toml (see src/bootstrap/config.toml.example for details) when building rustc/std: $ python bootstrap.py --config=config.toml
2016-05-18rustbuild: Pass -O to tests based on configurationAlex Crichton-0/+5
Currently rustbuild isn't detecting the `-O` flag for tests via the `--disable-optimize-tests` or not command line flag to `./configure`, and this commit patches up the support to pass `-O` by default.
2016-05-03rustbuild: Document many more parts of the buildAlex Crichton-0/+154
This commit expands the bootstrap build system's `README.md` as well as ensuring that all API documentation is present and up-to-date. Additionally a new `config.toml.example` file is checked in with commented out versions of all possible configuration values.