Migrate `cargo-raze` into `rules_rust` #590

* Support './' in lib.path targets * Add normal target to test

* WIP * Add option * Fix whitespace somewhere

* Complain to stderr about unused raze settings. * Provide more useful help message.

Fixes issue #1

…nternals) (#28) Refactor planning in the manner of `cargo metadata` (but keep using internals)

* Integrate the examples into cargo-raze * Add the remote examples as well * Add a README doc for remote examples * Fix the build after adding remote README * Remove examples for PR * Enable -f on `rm` so no error if dirs don't exist * Explicitly reset working directory back to original * Rename examples/README.md * Move the command exists check to a function * Make sure `command_exists` actually checks for existence * DIR -> REPO_ROOT

* Fixes for #36 * Updates for Cargo.toml * Fix some pathing issues with smoke-test.sh * Fix up travis not liking the new packaging

* Add the sha256 to the generated http_archive This is good practice to have them and we get them for free from Cargo. * Remove unused warnings * Update Cargo.lock The previous one doesn't build on my platform. * Address acmcarther@ suggestions

Now that rust_library/rust_binary supports it.

Using native.existing_rules allow to use several crates.bzl file that would import the same crates without failing with duplicate rules.

* Pass 2 on remote git targets Previously this worked with the example because it actually resolved to crates.io even for "git" packages. The example was included before it was ready, and only because it relied exclusively on things already on crates.io did it compile in the first place. Tests back to compiling and running true -> True Fix a pathing issue Fix some unused imports * Suggested changes

* fix it * fix

* WIP: RM separate remote_ files * Simplify build_path slightly * More progress * Fix a test, save a life * Put the remote_crates back

* Update README.md Update the examples location now that they're inline to the main repository. * Update README.md Add back the OpenSSL example

* Wip the first * Wip the second * Clean code -- terrible formatter * Handle a lot of nits, but not the failing tests * Fix broken index insertion (debug_uggh) and rendering * Fix bug where root crate was expected to be vendored * Fix crate_context.build_path and update missing root crate test * Fix minor bugs with file generations * Fix tests and update some context var names

This rule is never used and was renamed in recent rust rules into rust_bechmark.

…ctory (#62) * Patch examples with latest cargo-raze generated output * Update deps, fix deprecation warnings, up to 0.1.0

…EADME file

* Update dependencies and fix for cargo 0.30.0 * Set non_cratesio_library's futures dep to a specific version

…70)

It is now automatically set by rules_rust. It should always be correct even for the build script with Bazel handling the configuration.

Newer version of rules_rust use ctx.actions.args() quoting that would quote "--cap-lints allow" as one argument. To be compatible with the new version use "--cap-lints=allow".

* native.new_git_repository is replaced by the skylark new_git_repository * native.new_http_archive is replaced by the skylark http_archive * Surround labels with the Label function so that crate.bzl can be used from other repositories.

* Update dependencies * Add support for Rust editions * Update metadata test fixture

* Bump Bazel on Travis to 0.17.1 * Update rules_rust in CI * Add bazel_version to the WORKSPACE

* Run blaze build commands independently so that 'set -e' properly fails * Fix spooky breakages

* Move main.rs into src/bin, add dump_metadata bin * Minor fixes * Clean up warnings

…ta (#84)" (#85) This reverts commit 966e872.

* Move main.rs into src/bin, add dump_metadata bin * Minor fixes * Clean up warnings * Move dump_metadata outside of cargo-raze/impl, add easy shell script, fix minor canonicalization issue * Make the formatting of tools consistent

* Add crate_context.has_eponymous_lib to fix bins depending on non-existent self-lib * Quick optimization * Tweak verbiage of has_eponymous_lib field doc * Add 'lib_target_name' param to CrateContext

@mfarrugi

I'm not sure why I originally added this constraint, but I'll remove it and see if CI accepts it. cc @mfarrugi

This option allows the user to set any suffix to the build files Default is BUILD Other values can be for example: BUILD.bazel Any value is accepted. This is to allow raze to follow the default behaviour of other bazel related tools that generate BUILD.bazel instead of BUILD firstly to separate what is generated and what is written and to avoid name collisions on case insensitive file systems (Windows + WSL) since some crates can have a directory named build which leads to cargo-raze unable to create a file called BUILD. A project having a directory named BUILD.bazel is much less likely or less to none chance.

Inconsistent casing where dep targets were slugified and target names were not caused errors when crate names were not all lowercase. This fixes the issue by removing the unnecessary slugifying from the target name (but keeps it in versioning) An example for this issue is with security-framework-sys which depends on the MacTypes-sys crate. To test this, I've added security-framework-sys as a dependency to both remote and vendored complicated_cargo_library

#99)

This should address #100

It looks like the code was refactored into the `impl` directory at some point, but the README link was never updated.

)

…on (#112)

Otherwise it ignores cmd line options

* [CI] Get CI functioning properly * [Planning] Allow proc-macros to export (#119) * Update to rust2018 * Update to latest cargo * Update tera to 1.0.0 * Do clippy fixups * Run rustfmt on code

…#128)

* Update cargo dependency (and add cargo_platform) * Remove debug stuff

* Use CargoSubcommandMetadataFetcher by default * Parameterize CargoSubcommandMetadataFetcher on cargo bin * Update cargo dependency (and add cargo_platform) * Fix SourceId parsing (from cargo metadata exec) * Support forcing cargo-internals mode, support specifying cargo bin path * fix docopts and reenable format-version * Fix docopts * Remove debug stuff * Minor fix to Options string

…er (#140) This addresses the panic described in google/cargo-raze#139 (comment).

* Clean-up no-op conditional * Simplify taking build script target further

This is required for bazel 3.1.0; otherwise bazelbuild/bazel#7793 causes build failures.

* Allow customizing BUILD files through additional_build_file This option allows the user to append custom content to the generated BUILD files. For example, one can use it to include custom Bazel targets for building non-Rust parts of the crate. Fixes #58. * Trim extra whitespace in crates.bzl from the patch template

Travis is failing with the following error: ERROR: /home/travis/.cache/bazel/_bazel_travis/9838a0d5b93391760180ad93f9f7ea99/external/io_bazel_rules_rust/rust/repositories.bzl:3:1: file '@bazel_tools//tools/build_defs/repo:utils.bzl' does not contain symbol 'maybe' Source: https://travis-ci.org/github/google/cargo-raze/builds/686275069 The maybe symbol was added to "//tools/build_defs/repo" in June, 2019. However, the version of Bazel used within Travis is fairly old (0.17.1); this change moves it to the most recent revision of Bazel.

* Remove CargoInternalsMetadataFetcher * Use cargo_metadata explicitly * [planning] Reduce usage of unwrap * [planning] Resolve clippy lints * [planning] Sanitize version, add regression test

This replaces `CargoResult` with anyhow's `Result`, and uses `SourceId` from cargo_lock instead. As far as I can tell, we lose 101 dependencies total :)

Signed-off-by: Gregg Reynolds <601396+mobileink@users.noreply.github.com>

…163) It looks like a `-` was missing in #161, which added additional_env support. This causes a blank line with extra whitespace to show up relative to 0.3.1, or older. This adds that back in, which matches the rest of the template file and resolves the whitespace issue.

* Create untested fix for aliased dependencies * Fix a few bugs * Fix length in templates * Final template fix * Fix templates and replace hyphens with underscores in renamed package * Use maps to avoid unwraps * Make changes based on comments from dfreese * Pull alias strings out to a new struct. * Change rust_binary template to match rust_library changes. * Remove sanitize_name and use sanitize_ident * Add unit test for aliased dependencies * Run cargo fmt

Instead of a custom genrule. See #320

Use new cargo_build_script_run rule

This was brought up in #68.

This will be needed for #166

I want to optimistically default to generating build scripts by default.

This allows an unconditional transition to the `exec` config, rather than needing a conditional transition (which cannot transition to the `exec` config, only to the `host` config). Requires rules_rust commit c409198 or later.

* Support more robust SPDX licenses * Update template and change nomenclature * Fix some bugs and add more tests * Fix expression assignments * Return LicenseData and fix nomenclature * Implement default for license

System crates build scripts may produce environment variables that may be used by their direct dependencies build script. For example openssl-sys generates DEP_OPENSSL_VERSION variable that is then used by openssl crate build scripts. Co-authored-by: Alexei Filippov <alph@apple.com>

Also fix: * remote folder created on dry run * remote/BUILD folder does not use prefix path parameter

The tags can be used to exclude cargo-raze generated rules from, e.g. "//...:all" targets. It is useful to prevent Bazel from building unsupported targets in multiplatform configurations. Co-authored-by: Alexei Filippov <alph@apple.com>

Since the switch to the cargo_build_script rule, the buildrs_additional_environment_variables was no longer working, this change add this support back. Fixes #179

Proc macro crates were split off into their own field in #164 and then PR #166 changed handling of build scripts to invoke cargo_build_script, however, build dependencies can also have proc macros. This was an issue for markup5ever, which has a build dependency that transitively depends on serde_derive. Fixes #181

Adds an additional error for non-unicode paths, which was previously a TODO in terms of handling. #178 provided a similar solution.

…185) This change makes it so that the `Cargo.toml` file can live within the [recommended location](https://doc.rust-lang.org/cargo/guide/project-layout.html) and `cargo-raze` will output content into a [Bazel workspace](https://docs.bazel.build/versions/master/build-ref.html#workspace) in a way that better matches the expectations set by [Bazel's naming conventions](https://docs.bazel.build/versions/master/build-ref.html) ``` ├── BUILD ├── Cargo.lock │ ├── Cargo.toml <- HERE │ ├── README.md ├── cargo │ │ │ ├- <- INSTEAD OF HERE │ │ │ └── libloading_global_static.BUILD └── src └── main.rs ``` This makes it easier to transition Rust projects to start using Bazel since users no longer have to move their `Cargo.toml` files and the use of `workspace_path` (which looks like a [Label](https://docs.bazel.build/versions/master/build-ref.html#labels)) makes more sense. Getting started with Bazel/cargo-raze should now only require users to add the `[raze]` section to their existing `Cargo.toml` file and run `cargo raze` (assuming they're using the remote genmode, but otherwise could vendor the packages and do the same thing). The smoke-tests show the up to date examples but I wasn't sure if I should update the [actual examples](https://github.com/google/cargo-raze/tree/master/examples) with the generated results of the smoke-tests.

…#202)

…or testing/examples (#191)

Fixes #198

@generated

…r defects. (#207) This is a followup on comments made in #199 The `crates.bzl` file generated in the event that no crates are defined looks like the following ```python """ @generated cargo-raze crate workspace functions DO NOT EDIT! Replaced on runs of cargo-raze """ load("@bazel_tools//tools/build_defs/repo:git.bzl", "new_git_repository") # buildifier: disable=load load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") # buildifier: disable=load load("@bazel_tools//tools/build_defs/repo:utils.bzl", "maybe") # buildifier: disable=load def raze_fetch_remote_crates(): """No crates were detected in the source Cargo.toml. This is a no-op""" pass ```

* Add manual tag to all generated targets * Explicitly separate remote and vendored examples * Fixed buildifier warning * Updated examples

@generated

Similar to #54 this pull request adds support for generating Bazel targets for multiple platforms. This is still kinda **WIP** but I wanted to share. I'll update this description as the feature evolves but for now am looking for any insight on what may be missing for the initial release of this feature. Output `BUILD` file: ```python """ @generated cargo-raze crate build file. DO NOT EDIT! Replaced on runs of cargo-raze """ # buildifier: disable=load load( "@io_bazel_rules_rust//rust:rust.bzl", "rust_binary", "rust_library", "rust_test", ) # buildifier: disable=load load("@bazel_skylib//lib:selects.bzl", "selects") package(default_visibility = [ # Public for visibility by "@raze__crate__version//" targets. # # Prefer access through "//cbindgen/raze", which limits external # visibility to explicit Cargo.toml dependencies. "//visibility:public", ]) licenses([ "notice", # MIT from expression "MIT" ]) # Generated targets # Unsupported target "atty" with type "example" omitted # buildifier: leave-alone rust_library( name = "atty", crate_type = "lib", deps = [ ] + selects.with_or({ # cfg(unix) ( "@io_bazel_rules_rust//rust/platform:aarch64-apple-ios", "@io_bazel_rules_rust//rust/platform:aarch64-linux-android", "@io_bazel_rules_rust//rust/platform:aarch64-unknown-linux-gnu", "@io_bazel_rules_rust//rust/platform:arm-unknown-linux-gnueabi", "@io_bazel_rules_rust//rust/platform:i686-apple-darwin", "@io_bazel_rules_rust//rust/platform:i686-linux-android", "@io_bazel_rules_rust//rust/platform:i686-unknown-freebsd", "@io_bazel_rules_rust//rust/platform:i686-unknown-linux-gnu", "@io_bazel_rules_rust//rust/platform:powerpc-unknown-linux-gnu", "@io_bazel_rules_rust//rust/platform:s390x-unknown-linux-gnu", "@io_bazel_rules_rust//rust/platform:x86_64-apple-darwin", "@io_bazel_rules_rust//rust/platform:x86_64-apple-ios", "@io_bazel_rules_rust//rust/platform:x86_64-linux-android", "@io_bazel_rules_rust//rust/platform:x86_64-unknown-freebsd", "@io_bazel_rules_rust//rust/platform:x86_64-unknown-linux-gnu", ): [ "@rules_rust_cbindgen__libc__0_2_76//:libc", ], "//conditions:default": [], }) + selects.with_or({ # cfg(windows) ( "@io_bazel_rules_rust//rust/platform:i686-pc-windows-gnu", "@io_bazel_rules_rust//rust/platform:x86_64-pc-windows-gnu", ): [ "@rules_rust_cbindgen__winapi__0_3_9//:winapi", ], "//conditions:default": [], }), srcs = glob(["**/*.rs"]), crate_root = "src/lib.rs", edition = "2015", rustc_flags = [ "--cap-lints=allow", ], version = "0.2.14", tags = [ "cargo-raze", "manual", ], crate_features = [ ], ) ``` Note that the `deps` section can be filtered down to a whitelist of platform triples using the new `targets` setting. ```toml targets = [ "aarch64-unknown-linux-gnu", "i686-apple-darwin", "i686-pc-windows-gnu", "i686-unknown-linux-gnu", "powerpc-unknown-linux-gnu", "x86_64-apple-darwin", "x86_64-pc-windows-gnu", "x86_64-unknown-linux-gnu", ] ``` The list above creates the following diff in the output BUILD file. ```diff diff --git a/cbindgen/raze/remote/atty-0.2.14.BUILD.bazel b/cbindgen/raze/remote/atty-0.2.14.BUILD.bazel index dfcf387..6002194 100644 --- a/cbindgen/raze/remote/atty-0.2.14.BUILD.bazel +++ b/cbindgen/raze/remote/atty-0.2.14.BUILD.bazel @@ -48,21 +48,12 @@ rust_library( }) + selects.with_or({ # cfg(unix) ( + "@io_bazel_rules_rust//rust/platform:aarch64-unknown-linux-gnu", "@io_bazel_rules_rust//rust/platform:i686-apple-darwin", "@io_bazel_rules_rust//rust/platform:i686-unknown-linux-gnu", + "@io_bazel_rules_rust//rust/platform:powerpc-unknown-linux-gnu", "@io_bazel_rules_rust//rust/platform:x86_64-apple-darwin", "@io_bazel_rules_rust//rust/platform:x86_64-unknown-linux-gnu", - "@io_bazel_rules_rust//rust/platform:aarch64-apple-ios", - "@io_bazel_rules_rust//rust/platform:aarch64-linux-android", - "@io_bazel_rules_rust//rust/platform:aarch64-unknown-linux-gnu", - "@io_bazel_rules_rust//rust/platform:powerpc-unknown-linux-gnu", - "@io_bazel_rules_rust//rust/platform:arm-unknown-linux-gnueabi", - "@io_bazel_rules_rust//rust/platform:s390x-unknown-linux-gnu", - "@io_bazel_rules_rust//rust/platform:i686-linux-android", - "@io_bazel_rules_rust//rust/platform:i686-unknown-freebsd", - "@io_bazel_rules_rust//rust/platform:x86_64-apple-ios", - "@io_bazel_rules_rust//rust/platform:x86_64-linux-android", - "@io_bazel_rules_rust//rust/platform:x86_64-unknown-freebsd", ): [ "@rules_rust_cbindgen__libc__0_2_76//:libc", ], ```

* Add push-new-version.sh for pushing versions of the crate * Rename the file to 'publish-new-version' to reflect the commit message. * Fix whitespace * Accept crate version as regular argument. Add documentation * More wordsmithing tweaks * Address comments and google-sh lints * Use --release during cargo build * Add explanation for the cargo build

This change improves the speed of tests by combining all build steps into 1 command and avoids having to startup Bazel for each set of tests. There is also now a test for a project that has no dependencies. This tests that raze doesn't generate broken files in this case Finally, this change adds a launch_test macro which is used to create tests for each example binary and launch it as part of a test. This macro was created to try and keep the examples as straight forward as possible (not having to dump some test code in there). This should make it easier to catch regressions.

* Updated .lock files for existing examples * Updated vendored example README's * Fixed compiler warnings * Updated examples and removed all vendored source code except generated BUILD files

The use of `&String` in function parameters is discouraged in favor of `&str` as it otherwise forces passing heap-allocated values (which doesn't include e.g. string literals).

Change &String function parameters to &str

Before this change, the get_matching_bazel_triples would only allow matching cfg(...) targets. It seems that the intended behaviour was to allow passing triples (such as `x86_64-unknown-linux-gnu`) directly, as per the `format!("cfg(target = \"{}\")", target)` replacement at the beginning of the function. Unfortunately, the match was missing the right case below (`Predicate::Target(tp)` only matches builtin `target_{arch,os,...}`). This makes this function more consistent with `is_bazel_supported_platform` above, and it seems to solve a bug where target specific dependencies specified with triples (such as is the case for the `winapi` crate in one of the `complicated_cargo_library` example) would be ignored.

* Updated default registry url * Updated examples

* Updated smoketest WORKSPACE file * Updated examples

This allows us to generate a strip_prefix directive in the new_git_repository call.

* platform-specific aliases were missing * avoid extra newline when aliases is omitted * update examples via smoke_test The length check in common_attrs is only checking if there are any targeted deps, so targeted deps without any aliases end up with an empty aliases entry instead of it being excluded completely. What we really want to do if check if deps.aliased_dependencies is non-empty for any of the provided targeted deps, but I'm not sure how/if that can be done in Tera.

* Added binary_dependency example * Updated examples

`cargo vendor` currently outputs helptext regarding updating `.cargo/config.toml` in order to replace crates.io sources with the vendored sources, e.g.: ``` ➜ cargo vendor --versioned-dirs To use vendored sources, add this to your .cargo/config for this project: [source.crates-io] replace-with = "vendored-sources" [source.vendored-sources] directory = "path/to/vendor" ``` If a user adds this to their `.cargo/config.toml` configuration prior to the first run of `cargo vendor`, then `cargo generate-lockfile` and `cargo vendor --locked` will fail to update the lockfile. This patch removes the instructions related to generating the lockfile with `cargo generate-lockfile` (and the subsequent `--locked` flag to `cargo vendor`) , instead preferring to let `cargo vendor` manage the lockfile. The updated series of commands works in all cases, including first runs which already have a `.cargo/config.toml` file replacing `crates-io` sources. It's also now one command and one flag shorter, which some people might like too, I guess.

* Flipped default of `incompatible_relative_workspace_path` to true * Removed `incompatible_relative_workspace_path` flag from examples * Removed regression-test examples * Updated examples

* Moved `RazeError` into an `error` module * Addressed PR Feedback

* switch to MSVC targets on Windows gnu has been removed in favour of MSVC in rules_rust, so cargo-raze will need to be updated to match: dfce123 * Updated examples * add missing checksum update from Uebel: google/cargo-raze#254 * WORKSPACE needed to reflect date update of smoke-test.sh Co-authored-by: Andre Brisco <andre.brisco@gmail.com>

…vant components (#255)

* Turned the `rendering` module into a directory that contains all relevant components * Turned the `planning` module into a directory that contains all relevant components

* Moved `checks` out of `planning.rs` * Split `planning.rs` code into different files within the `planning` module

* Added a warning for when `genmode` is not explicitly set * Improved warning messages * Updatred smoketest * Updated examples * Addressed PR Feedback * Used Result over unreachable

* Updated build file format to be compliant with Bulidifier * Addressed buildifier defects * Fixed "the bug" * Addressed PR Feedback * Updated examples * Added note for future readers about ordering * Fixed one more templating issue * Updated examples * Leave dependencies alone for now * Updated examples

This is work pulled out of #276 Changes: * renamed settings::testing to settings::tests to be consistent with other modules * Ran cargo fmt

This is a _small_ quality of life change. Make it possible to use `indoc!` to declare inline strings.

* Moved template header into it's own file * Updated examples

* Updated smoketest bazel version and rules_rust hash * Updated examples

…ied on remote assets (#268)

* Accept `[package.metadata.raze]`, superseding `[raze]` Cargo sets aside the [`[package.metadata]`][md] namespace for use by third-party tools like `cargo-raze`. By specifying configuration under `[package.metadata.raze]` rather than `[raze]`, we avoid an “unused manifest key: raze” warning on every Cargo command. This patch teaches `cargo-raze` to accept either `[raze]` or the new `[package.metadata.raze]`. In case of conflict, it prints a warning and uses the value of `[package.metadata.raze]`. In the future, we can remove the `[raze]` key entirely if desired. Fixes #273. Changes outside of `impl/` generated by: ``` git ls-files -z ':!impl' | xargs -0 sed -i 's/\[raze/[package.metadata.raze/' ``` [md]: https://doc.rust-lang.org/cargo/reference/manifest.html#the-metadata-table Test Plan: With this patch, running `./smoke-test.sh` passes both before and after updating all the examples with the above `sed` command. Before the `sed` update, the smoke test prints the deprecation warning, as desired. wchargin-branch: toml-package-metadata-raze wchargin-source: 4932fedcc808b17506aadf4b69f6aa78850fe5c6 * [update patch] wchargin-branch: toml-package-metadata-raze wchargin-source: f2b7fb6fb07bd1f478aa1e8c14f7d623f86f69b3

Signed-off-by: Piotr Sikora <piotrsikora@google.com>

Raze settings come in the form of a [TOML] section like so ```toml [raze.crates.some-crate.'1.2.3'] some_new_setting = True ``` Where the version number (in the above example `1.2.3`) is a literal, hardcoded value. This works but is a little inflexible for dependencies, _especially_ dependencies that are transiant and update a lot (for instance `syn`). Since Cargo follows [Semver] we can use this fact, along with the richness of the exported and serialisable `semver::Version` types to perform section matching with [Semver] in the same fashion as Cargo itself. This means that the above example can be written with semver expressions, for example it can be written as: ```toml [raze.crates.some-crate.'1.2.*'] some_new_setting = True [raze.crates.some-crate.'~1.2.3'] some_new_setting = True [raze.crates.some-crate.'^1.2.3'] some_new_setting = True [raze.crates.some-crate.'=1.6.6'] some_new_setting = True ``` _Note_: Bare versions follow the semantics _as if they had_ specified a `^`, which is in keeping with [Cargo semver semantics] but is distinct from previous behaviour of raze (in which these would be interpreted as exacting or `=`). This is deliberate as we should aim to mirror the semantics of cargo as much as possible to avoid confusion. We presently do not allow for multiple matches in raze settings, this is intentional and is presented to the end user as an error. [TOML]: https://github.com/toml-lang/toml [Semver]: https://semver.org/spec/v2.0.0.html [Cargo semver semantics]: https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies-from-cratesio

This patch adds a `--version` flag that causes `cargo-raze` to print version info and exit. The functionality is built into Docopt, so it’s just a matter of hooking it up to the `CARGO_PKG_VERSION` env var. Test Plan: When invoking the binary to test, make sure to pass an extra `raze` arg so that docopt matches the `cargo raze` (not `cargo-raze`) pattern: ``` cargo run -- raze --version # or... cargo install --path . && cargo raze --version ``` Either invocation prints “cargo-raze 0.7.0” and a newline before exiting successfully. This format is consistent with the `--version` behavior of `cargo` and `rustc` themselves. wchargin-branch: cli-version wchargin-source: 11b3fadae75935076922e83c3b27151f7c55471a

* Fixed regression in template rendering * Updated examples

Signed-off-by: Piotr Sikora <piotrsikora@google.com>

The links attribute is needed to infer the name of environment variables to pass to sys crate dependencies.

* Added cargo workspaces support * Updated smoketest * Updated examples * Addressed PR feedback * Addressed PR feedback * Addressed PR feedback * Addressed PR feedback * Addressed PR feedback * Addressed PR feedback * Addressed PR feedback * Addressed PR feedback * Slight cleanup of new code * Addressed PR feedback * Addressed PR feedback * Addressed PR feedback * Fixed typos * Addressed PR feedback

* Small renaming and cleanup * Updated dependencies

* Added cargo_workspace smoketest * Updated examples

* Fixed cases where tests would fail when using `cargo_metadata::MetadataCommand` when the host had no network connectivity * Added some comments * Fixed typo

* Fixed bug where binary dependencies were having aliases rendered * Updated examples

* Add data deps attrs to CrateDependencyContext The attributes can only be set when using cargo-raze as a library right now, but when they are set, they will be reflected in the generated BUILD files. * Re-generate example BUILD files

* Moved the `crate::planning::checks` module to `crate::checks` * Added support for a `--manifest-path` argument * Updated documentation * Addressed PR feedback * Fixed missing docs * Removed AdditionalBuildFile enum * Updated examples * Addressed PR feedback * Addressed PR feedback * Fixed 'additional_build_file' complexity * Updated docs * Addressed PR feedback * Updated examples

* Renamed `workspace_member_dir` to `package_aliases_dir` * Updated documentation * Updated `package_aliases_dir` default to `"."` to avoid a change in behavior for existing users. * Updated examples

#516

* Settings are now parsed from Cargo metadata, not parsing toml files * Updated documentation and rules_rust definitions * Addressed PR feedback * Addressed PR feedback * Updated documentation * Updated documentation

* Added deprecation warnings * Updated smoketests * Updated examples * Addressed PR feedback. * Addressed PR feedback.

…ump. (#321)

* Added stardoc support * Updated examples * Addressed PR feedback * Updated examples * Addressed PR feedback

…ering package dependencies (#319) * The crates.bzl can be used to locate crates * Updated smoketest * Updated examples * It should not be an error that no dependencies are found. The use case here is users might want to stub out all the dependency sections of their crates such that subsequent runs of `cargo raze` will automatically add new dependencies. * Updated examples * New API has been flagged experimental * Updated examples * Updated more comments * Updated examples * Updated documentation * Addressed PR feedback. * Updated examples * Addressed PR feedback * Updated examples * Addressed PR feedback * Updated examples * Fixed typo * Updated * Added experimental_api flag * Updated smoketest * Updated examples * Fixed buildifier defects * Updated examples * Addressed PR feedback * Updated examples * Addressed PR feedback * Updated examples * Addressed PR feedback * Updated examples * updated smoketest * Updated examples * Cleanup * Updated examples * Updated macros `crates` -> `crate_deps` and `all_crates` -> `all_crate_deps` * Updated examples

* Cargo raze can now be run from anywhere within a cargo workspace * Addressed PR feedback

…#331)

… shouldn't have been (#337) * Fixed a bug where export_files was being rendered into BUILD files it shouldn't have been * Updated examples * Fixed ordering issue

* Added `render_package_aliases` flag to allow for disabling the rendering of alias targets * Updated smoketest * Updated examples

Per [issue 335], I didn't find these docstrings very helpful. The important bit of this property appears to be "this is where outputs go". Try to make that clearer in the property docstring and the README. [issue 335]: google/cargo-raze#335

…targets (#343) * Added settings for adding additional content to rendered `cargo_build_script` targets * Restored `CrateDependencyContext` fields

* fix(subplanners): Match aliased dependencies by name and semver * Simplify the aliased dependency test

* Added check for missing checksums * Deleted `CargoWorkspaceFiles` and added support for `--generate-lockfile` * Addressed PR feedback

…342) * Rust library and binary dependencies are all sorted before rendering * Updated examples * Addressed PR feedback * Addressed PR feedback

* Restructured project to be buildable with Bazel * Moved `dump_metadata` tool * Deleted smoke_test directory since examples are more authoritative now * Added bootstrapped cargo-raze outputs * Updated Bazel and rules_rust version * Addressed PR feedback

* Add initial bazelci/presubmit.yml * Remove superfluous whitespace

* intial attempt * add clippy in as comment * fix rustfmt errors

* Fixed dev dependencty aliases * Added dev dependency example

Most of these are efficiency clean-ups, by replacing modifications with _else, so that error path is evaluated lazily. Clippy is somewhat opinionated, so this does end up adjusting some conventions. However, on the whole, blindly accepting it as a linter is probably a win for the project.

)

* `rust_rules_workspace_name` now defaults to `rules_rust` * Renamed `io_bazel_rules_rust` to `rules_rust` throughout the workspace * Updated branch name for rules_rust

…gnores (#368)

A bug was fixed where the "CARGO" environment variable wasn't being when looking for a cargo binary. This has been corrected and is now in use.

…t's config_settings (#372)

Commits on Mar 5, 2018

Run Rustfmt over everything (#9 )

acmcarther committed Mar 5, 2018

Configuration menu

View commit details

Copy full SHA for f0ddd97

Browse repository at this point

Copy the full SHA

f0ddd97 View commit details

Browse the repository at this point in the history

Commits on Apr 14, 2018

Add missing license header files (#46 )

acmcarther committed Apr 14, 2018

Configuration menu

View commit details

Copy full SHA for ca9321b

Browse repository at this point

Copy the full SHA

ca9321b View commit details

Browse the repository at this point in the history

Commits on May 18, 2018

Fix link to settings.rs

acmcarther committed May 18, 2018

Configuration menu

View commit details

Copy full SHA for c864bbf

Browse repository at this point

Copy the full SHA

c864bbf View commit details

Browse the repository at this point in the history

Commits on Jun 25, 2018

Run the formatter in isolation

acmcarther committed Jun 25, 2018

Configuration menu

View commit details

Copy full SHA for 2e4128f

Browse repository at this point

Copy the full SHA

2e4128f View commit details

Browse the repository at this point in the history

Commits on May 20, 2019

Update examples directory

acmcarther committed May 20, 2019

Configuration menu

View commit details

Copy full SHA for bdc7076

Browse repository at this point

Copy the full SHA

bdc7076 View commit details

Browse the repository at this point in the history

Commits on Jul 5, 2020

Update to 0.3.7

acmcarther committed Jul 5, 2020

Configuration menu

View commit details

Copy full SHA for 439f393

Browse repository at this point

Copy the full SHA

439f393 View commit details

Browse the repository at this point in the history

Commits on Jul 10, 2020

Update to 0.3.8

David Freese committed Jul 10, 2020

Configuration menu

View commit details

Copy full SHA for f77ba88

Browse repository at this point

Copy the full SHA

f77ba88 View commit details

Browse the repository at this point in the history

Commits on Dec 9, 2020

Updated dependencies (#315 )

UebelAndre committed Dec 9, 2020

Configuration menu

View commit details

Copy full SHA for d10b005

Browse repository at this point

Copy the full SHA

d10b005 View commit details

Browse the repository at this point in the history

Commits on Dec 12, 2020

support compile_data (#308 )

#516

dae committed Dec 12, 2020

Configuration menu

View commit details

Copy full SHA for 06c3c46

Browse repository at this point

Copy the full SHA

06c3c46 View commit details

Browse the repository at this point in the history

Commits on Jan 23, 2021

Updated dependencies (#350 )

UebelAndre committed Jan 23, 2021

Configuration menu

View commit details

Copy full SHA for 8e3b6a8

Browse repository at this point

Copy the full SHA

8e3b6a8 View commit details

Browse the repository at this point in the history

Migrate cargo-raze into rules_rust #590

Migrate cargo-raze into rules_rust #590

Commits on Mar 5, 2018

Commits on Mar 8, 2018

Commits on Mar 11, 2018

Commits on Mar 12, 2018

Commits on Mar 14, 2018

Commits on Mar 15, 2018

Commits on Mar 20, 2018

Commits on Mar 27, 2018

Commits on Mar 30, 2018

Commits on Apr 6, 2018

Commits on Apr 14, 2018

Commits on May 18, 2018

Commits on Jun 5, 2018

Commits on Jun 6, 2018

Commits on Jun 21, 2018

Commits on Jun 23, 2018

Commits on Jun 25, 2018

Commits on Jun 26, 2018

Commits on Aug 27, 2018

Commits on Sep 22, 2018

Commits on Oct 22, 2018

Commits on Nov 5, 2018

Commits on Nov 8, 2018

Commits on Nov 9, 2018

Commits on Nov 10, 2018

Commits on Dec 1, 2018

Commits on Jan 9, 2019

Commits on Jan 10, 2019

Commits on Jan 22, 2019

Commits on Feb 4, 2019

Commits on Apr 5, 2019

Commits on Apr 6, 2019

Commits on Apr 16, 2019

Commits on Apr 26, 2019

Commits on Apr 27, 2019

Commits on May 20, 2019

Commits on May 22, 2019

Commits on May 23, 2019

Commits on May 24, 2019

Commits on Jul 5, 2019

Commits on Aug 26, 2019

Commits on Aug 28, 2019

Commits on Sep 23, 2019

Commits on Dec 10, 2019

Commits on Dec 19, 2019

Commits on Jan 6, 2020

Commits on Jan 31, 2020

Commits on Feb 16, 2020

Commits on Apr 1, 2020

Commits on Apr 23, 2020

Commits on Apr 30, 2020

Commits on May 11, 2020

Commits on May 12, 2020

Commits on May 13, 2020

Commits on May 14, 2020

Commits on May 26, 2020

Commits on Jun 3, 2020

Commits on Jun 5, 2020

Commits on Jun 8, 2020

Commits on Jun 10, 2020

Commits on Jun 12, 2020

Commits on Jun 15, 2020

Commits on Jun 16, 2020

Commits on Jun 17, 2020

Commits on Jun 29, 2020

Commits on Jul 1, 2020

Commits on Jul 5, 2020

Commits on Jul 8, 2020

Commits on Jul 10, 2020

Commits on Aug 13, 2020

Commits on Aug 21, 2020

Commits on Aug 24, 2020

Commits on Aug 26, 2020

Commits on Aug 27, 2020

Commits on Aug 28, 2020

Commits on Sep 8, 2020

Commits on Sep 9, 2020

Commits on Sep 15, 2020

Migrate `cargo-raze` into `rules_rust` #590

Migrate `cargo-raze` into `rules_rust` #590