| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
|
| |
Ubuntu LTS has a gcc version that generates broken code for certain newer C++
constructs. Change the code to avoid those constructs.
Fixes #68.
--
Change-Id: 4a0420a6c996d0e7785e5cdf39bbd0602472449f
MOS_MIGRATED_REVID=90739507
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90737433
|
|
|
|
|
|
|
| |
--embed_label
--
MOS_MIGRATED_REVID=90723863
|
|
|
|
|
|
| |
--
Change-Id: b2b38d09285950c8ef745dbf2cbd281e09e7a11e
MOS_MIGRATED_REVID=90721856
|
|
|
|
|
|
|
|
|
| |
This allows removing most /[]/ prefixes from all output file names in all
tests that inherit from FoundationTestCase; that, in turn, allows us to switch
the workspace root to a neutral name, such as /workspace/.
--
MOS_MIGRATED_REVID=90720852
|
|
|
|
|
|
|
| |
Fixes https://github.com/google/bazel/issues/90.
--
MOS_MIGRATED_REVID=90717991
|
|
|
|
|
|
|
| |
CppCompilationActionContext, which can be overridden by some modules.
--
MOS_MIGRATED_REVID=90716346
|
|
|
|
|
|
|
| |
was ignoring the actionContext, which it shouldn't have been.
--
MOS_MIGRATED_REVID=90714138
|
|
|
|
|
|
|
| |
Note that we probably want to change the discardMetadata signature to no longer take an argument, since we have per-action metadata handling. However, I'd like to know that that's the source of the crash, if it is, which is why I'm not removing the argument right now.
--
MOS_MIGRATED_REVID=90712991
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90710759
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90707320
|
|
|
|
|
|
| |
--
Change-Id: I67fa2a289cf82a4aee6b724429c1a1719c5649b4
MOS_MIGRATED_REVID=90707308
|
|
|
|
|
|
|
| |
See how it renders at http://bazel.io/docs/build-encyclopedia.html#py_binary.
--
MOS_MIGRATED_REVID=90706688
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90699667
|
|
|
|
|
|
|
| |
We currently hard-code this in two places, but should only do so in one
--
MOS_MIGRATED_REVID=90698681
|
|
|
|
|
|
|
| |
to be sure that no one uses it.
--
MOS_MIGRATED_REVID=90693216
|
|
|
|
|
|
|
| |
Some care was taken to make sure that we only log when a file is missing *after* the action is executed, when its failure to be present should force a build failure anyway, in order to avoid a source of memory pressure.
--
MOS_MIGRATED_REVID=90682557
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90649566
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rethrowing cause made sense a while ago, but now the only usages of this
method have a direct handle on the exception they want dealt with and
wrap the input with "new Exception(...)". Instead just pass the exception
along directly.
Also modified the comment in the unexpected case- the class referenced
does not exist anymore, from what I can tell, and thus the comment was
misleading.
--
MOS_MIGRATED_REVID=90623740
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90618694
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90616271
|
|
|
|
|
|
|
|
| |
This should avoid making unnecessary string copies.
--
Change-Id: I655f348ddeb3df47264a899a10d36086d2c2b596
MOS_MIGRATED_REVID=90614260
|
|
|
|
|
|
|
| |
now.
--
MOS_MIGRATED_REVID=90610846
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
This does not allow bazel help to be run from outside of a workspace
*** Original change description ***
Improve error message if WORKSPACE file is not found
--
MOS_MIGRATED_REVID=90608117
|
|
|
|
|
|
|
|
|
|
|
| |
Relative to the last try, add -B to Linux CROSSTOOL entry, and test
the result on OSX and Linux.
This should fix working with GCC cross compilers installed into
/usr/bin/ next to the host ld.
--
MOS_MIGRATED_REVID=90605463
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90574562
|
|
|
|
|
|
|
| |
better errors.
--
MOS_MIGRATED_REVID=90543663
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90543040
|
|
|
|
|
|
|
|
|
| |
We used to unconditionally add this file, but that doesn't make sense for crosstools that don't have it. Long-term, we need to get the name of this file from the CROSSTOOL file.
I was unable to test this because getting all of an older crosstool's dependencies into a test was too hard. But I manually verified that it works.
--
MOS_MIGRATED_REVID=90533610
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke bazel compile.sh build on Linux.
*** Original change description ***
Switch to @AutoValue for RuleDefintion.Metadata now that it is available.
--
MOS_MIGRATED_REVID=90529098
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90517845
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90516252
|
|
|
|
|
|
|
|
|
|
| |
No need to keep a separate variable at the top of the file, it is
simpler to just check the return value of getenv() directly in the call
site.
--
Change-Id: I896836206ccbf20743ef9679b10cec0cb7406122
MOS_MIGRATED_REVID=90505777
|
|
|
|
|
|
|
| |
instead of linear search to find line numbers and paths.
--
MOS_MIGRATED_REVID=90504135
|
|
|
|
|
|
|
|
| |
Bazel tests set -u and that prevented selection of test to run in a test
suite with --test_arg.
--
MOS_MIGRATED_REVID=90497934
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Use AutoValue in Bazel.
Only FunctionSignature uses AutoValue for now.
* Take advantage of AutoValue's .hashCode() and .equals() methods
to intern function signatures, thus saving space.
In the future, this will allow for better caching of optimizations
for all function calls and struct accesses, base on pairs of
FunctionSignature and CallerSignature or list of names and field name.
--
MOS_MIGRATED_REVID=90482300
|
|
|
|
|
|
|
|
| |
Add the Google auto generators for Java, for the sake of using AutoValue.
Include dependencies apache commons collections and apache velocity.
--
MOS_MIGRATED_REVID=90482044
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90455131
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90441648
|
|
|
|
|
|
|
|
|
|
|
| |
ActionInputFileCache when given a digest to do a reverse lookup so that metadata can be more easily retrieved.
Discovered inputs are no longer ever put into SingleBuildFileCache, so it is safe to roll this forward now
Because of code changes (meant to ensure the safety of this change), there were conflicts that had to be manually resolved.
--
MOS_MIGRATED_REVID=90425783
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90418160
|
|
|
|
|
|
|
| |
Specifies function return values. Replaces old "builder" terminology. Removes bad advice.
--
MOS_MIGRATED_REVID=90417023
|
|
|
|
|
|
|
| |
functionality is gone.
--
MOS_MIGRATED_REVID=90289916
|
|
|
|
|
|
|
|
|
| |
ExtraAction itself.
This makes ExtraAction simpler to understand (IMO). It's also a prerequisite for some simplifications we're making in core.
--
MOS_MIGRATED_REVID=90288551
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90282858
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
New ZipCombiner creates malformed output ZIP files when input ZIP files contain more than 65535 entries, the maximum amount for non-64-bit ZIP files.
*** Original change description ***
Rewrite of ZipCombiner to improve performance and maintainability. Added devtools/build/zip to allow reading and writing of ZIP files without requiring decompressing file data to manipulate them.
ZipCombiner API has some changes. ZipCombiner#addZip takes a File instead of InputStream. ZipCombiner#addFile takes a ZipFileEntry instead of DirectoryEntryInfo
--
MOS_MIGRATED_REVID=90279976
|
|
|
|
|
|
|
| |
This was making Bazel's bootstrap_test fail.
--
MOS_MIGRATED_REVID=90270050
|
|
|
|
|
|
|
|
|
|
|
| |
(i) Change the semantics of KeyedLocker.AutoUnlocker#close such that it can be called at most once per AutoUnlocker instance.
(ii) Change KeyedLocker.AutoUnlocker#close to throw a IllegalUnlockException (RuntimeException) on error, rather than leave the behavior intentionally underspecified.
(iii) explicitly mention in AutoLocker#lock that a thread can call lock(k) multiple times before unlocking. Combined with (i), this implies that KeyedLocker#lock implementations will want to return fresh AutoUnlocker instances.
These semantics are bit nicer to use anyway, but I also want them because I will soon be introducing KeyedLocker#lockBatch, and it's much easier to specify that given the above.
--
MOS_MIGRATED_REVID=90259645
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90255287
|
|
|
|
|
|
|
| |
Fixes #91.
--
MOS_MIGRATED_REVID=90185784
|