bazel
/
rules_cc
mirror of https://github.com/bazelbuild/rules_cc
2
0
Fork 0
Code Issues Releases Activity
411 Commits 15 Branches 20 Tags 1.9 MiB
Commit Graph

4 Commits

Author SHA1 Message Date
Googler e68ae76a67 Allow the C++ toolchain config rules comparator script to not need toolchain_identifier argument when both --before and --after arguments are CToolchains (coming from Starlark rules instead of CROSSTOOL proto) 
We don't need to select a toolchain by the identifier when we get the proto from Starlark rules because in that case the proto contains a single toolchain.
The difference in toolchain_identifier field between the first and the second proto file will be caught as any other field.

RELNOTES: None.
PiperOrigin-RevId: 262543753
Change-Id: I1e66ee302bf551ade883c217f6269f44382393c0
 2019-08-09 05:43:22 -07:00
Googler da4639bd1f Actually cause the comparator / test to fail when there is an error reading one 
of the toolchains.

Cosmetic spacing fixes for strings that will be concatenated and fixed a typo.

PiperOrigin-RevId: 229961708
 2019-01-18 11:20:25 -08:00
rosica f64680e017 Make ctoolchain_comparator.py throw exit(1) when CToolchains differ 
While here, Also fix _read_crosstool_or_ctoolchain_proto to actually return the CToolchain found in the CROSSTOOL file, and add some missing \n.

RELNOTES: None.
PiperOrigin-RevId: 229926500
 2019-01-18 07:37:16 -08:00
rosica 175f81c847 Add a script for comparing CToolchian built from different CROSSTOOL/Ctoolchain proto text files 
Progress towards #5380

RELNOTES: None.
PiperOrigin-RevId: 228312688
 2019-01-09 08:59:20 +01:00