| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
cxx_builtin_include directories which start with "%workspace%/" are taken
to be relative to the build workspace, and not relative to crosstool-top.
RELNOTES[NEW]: cpxx_builtin_include_directory specifications allow more flexibility.
--
MOS_MIGRATED_REVID=105789270
|
|
|
|
|
|
|
|
|
|
|
| |
android_library rule when the android_library is being used as a forwarding rule
(i.e., has no sources).
RELNOTES: When used as a forwarding rule (i.e., has no sources), android_library
will also forward any exported_plugins in its dependencies.
--
MOS_MIGRATED_REVID=105787789
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks many android targets in the depot.
*** Original change description ***
Trying again with checking for the presence of the "resources" attribute.
Change the resource dependency handling to separate between the transitive and direct resources from libraries.
This slightly increases the complexity of resource propagation. The initial algorithm was to simply merge all transitive ResourceContainers together with any new ResourceContainer and propagate them via the AndroidResourcesProvider. The new algorithm is encapsulated inside a new ResourceDependencies class which...
***
ROLLBACK_OF=105631635
--
MOS_MIGRATED_REVID=105752015
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change the resource dependency handling to separate between the transitive and direct resources from libraries.
This slightly increases the complexity of resource propagation. The initial algorithm was to simply merge all transitive ResourceContainers together with any new ResourceContainer and propagate them via the AndroidResourcesProvider. The new algorithm is encapsulated inside a new ResourceDependencies class which works as follows:
1. Collect resources from the deps into transitive and direct NestedSets
2. If a rule provides a ResourceContainer, merge the transitive and direct into a new transitive set
3. Export the provider
This results having a rule without resources "forward" the merged sets of transitive and direct resources to the next rule.
--
MOS_MIGRATED_REVID=105631635
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105624527
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks [].
*** Original change description ***
Change the resource dependency handling to separate between the transitive and direct resources from libraries.
This slightly increases the complexity of resource propagation. The initial algorithm was to simply merge all transitive ResourceContainers together with any new ResourceContainer and propagate them via the AndroidResourcesProvider. The new algorithm is encapsulated inside a new ResourceDependencies class which works as follows:
1. Collect resources from the deps into transitive and...
***
--
MOS_MIGRATED_REVID=105598448
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105596479
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and direct resources from libraries.
This slightly increases the complexity of resource propagation. The initial algorithm was to simply merge all transitive ResourceContainers together with any new ResourceContainer and propagate them via the AndroidResourcesProvider. The new algorithm is encapsulated inside a new ResourceDependencies class which works as follows:
1. Collect resources from the deps into transitive and direct NestedSets
2. If a rule provides a ResourceContainer, merge the transitive and direct into a new transitive set
3. Export the provider
This results having a rule without resources "forward" the merged sets of transitive and direct resources to the next rule.
--
MOS_MIGRATED_REVID=105515074
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105511114
|
|
|
|
|
|
|
|
|
| |
and mainGroup in xcodeproj.
RELNOTES: Adds --override_workspace_root blaze flag to hand-set workspace_root and mainGroup in xcodeproj.
--
MOS_MIGRATED_REVID=105484952
|
|
|
|
|
|
|
| |
Eliminate side-effect in command_line_srcs and hide the internal class.
--
MOS_MIGRATED_REVID=105480701
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before:
ERROR: No toolchain found for cpu 'x84'.
After:
ERROR: No toolchain found for cpu 'x84'. Valid cpus are: [
armeabi,
armeabi-v7a,
armeabi-v7a-hard,
armeabi-thumb,
armeabi-v7a-thumb,
armeabi-v7a-hard-thumb,
arm64-v8a,
mips,
mips64,
x86,
x86_64,
].
--
MOS_MIGRATED_REVID=105324190
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
legible by putting each flag combination on its own line.
E.g. from this:
ERROR: No toolchain found for --cpu='foo' --compiler='bar' --glibc='baz'. Valid toolchains are: [ --cpu='armeabi-v7a' --compiler='compiler' --glibc='armeabi-v7a', --cpu='armeabi-v7a' --compiler='compiler' --glibc='armeabi-v7a', --cpu='local' --compiler='compiler' --glibc='local', --cpu='darwin' --compiler='compiler' --glibc='macosx', --cpu='freebsd' --compiler='compiler' --glibc='local', --cpu='k8' --compiler='windows_mingw' --glibc='local', --cpu='k8' --compiler='windows_msys64_mingw64' --glibc='local', --cpu='k8' --compiler='windows_clang' --glibc='local',].
to this:
ERROR: No toolchain found for --cpu='foo' --compiler='bar' --glibc='baz'. Valid toolchains are: [
--cpu='armeabi-v7a' --compiler='compiler' --glibc='armeabi-v7a',
--cpu='armeabi-v7a' --compiler='compiler' --glibc='armeabi-v7a',
--cpu='local' --compiler='compiler' --glibc='local',
--cpu='darwin' --compiler='compiler' --glibc='macosx',
--cpu='freebsd' --compiler='compiler' --glibc='local',
--cpu='k8' --compiler='windows_mingw' --glibc='local',
--cpu='k8' --compiler='windows_msys64_mingw64' --glibc='local',
--cpu='k8' --compiler='windows_clang' --glibc='local',
].
(notice there is a duplicate toolchain)
--
MOS_MIGRATED_REVID=105313547
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105301167
|
|
|
|
|
|
|
| |
not be locked to iOS SDK.
--
MOS_MIGRATED_REVID=105231425
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now prints:
//foo:bar (cached) PASSED in 0.1s
instead of:
//foo:bar (1/0 cached) PASSED
Fixes #218.
--
MOS_MIGRATED_REVID=105210302
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105204997
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added a flag which allows the user to specify the android compiler.
This commit also disconnects the android compiler from the main
--compiler flag. Changing the --compiler flag won't change the
compiler used by the android rules.
--
Change-Id: I788d3a353a1cc304e1c015b9dd283258e6e172d4
Reviewed-on: https://bazel-review.googlesource.com/2112
MOS_MIGRATED_REVID=105203751
|
|
|
|
|
|
|
| |
This requires changing all "//tools/language:target" implicit dependencies to "@tools//tools/language:target".
--
MOS_MIGRATED_REVID=105193805
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105175791
|
|
|
|
|
|
|
|
| |
This supersedes bin/gen files on Android SDK. The fields are removed
entirely since the proto isn't public yet.
--
MOS_MIGRATED_REVID=105130701
|
|
|
|
|
|
|
|
|
| |
This is superfluous because when an action is executed, the cwd is always the exec root we always pass exec paths on the command line.
This is necessary because this doesn't work if the proto compiler tool is not in the main repository.
--
MOS_MIGRATED_REVID=105057016
|
|
|
|
|
|
|
| |
(determined from xcrun) for applicable actions
--
MOS_MIGRATED_REVID=105000617
|
|
|
|
|
|
|
|
|
|
| |
The value of new flag --ios_signing_cert_name takes precedence over any specified
provisioning profilefor purposes of signing.
RELNOTES: --ios_signing_cert_name allows specifying a cert for iOS app signing
--
MOS_MIGRATED_REVID=104961817
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104886879
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104862806
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104861832
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104845397
|
|
|
|
|
|
|
|
|
| |
to construct and export a J2ObjC-code-and-dep-only view of the ObjcProvider, which is then used to create the compile action for J2ObjC-generated code at the binary level. This greatly reduces the number of input artifacts for such actions.
Also export header search paths at the edges (J2ObjcAsepct and J2ObjcProtoAspect) instead of in j2objc_library. This change removes some unnecessary header search paths.
--
MOS_MIGRATED_REVID=104821185
|
|
|
|
|
|
|
| |
locations.
--
MOS_MIGRATED_REVID=104797906
|
|
|
|
|
|
|
|
|
|
| |
step.
This should make ThinLTO work with .o files that are not generated by
compiling C++ in a cc_library()
--
MOS_MIGRATED_REVID=104764111
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, module maps contain both "use <module>" entries that specify which
modules the current module map depends on, and "extern module" entries that
provide paths where to load the dependent module maps from.
This change adds a feature "module_map_without_extern_module", which instructs
blaze to not write the "extern module" entries into the module map. Instead,
the crosstool needs to add -fmodule-file flags for each dependent module file
where needed for the compile via the new build variable
"dependent_module_map_files".
Note that the feature is phrased negatively ("_without_") in order to simplify
the roll-out of this feature: as long as crosstools do not specify any
features, they still want the old behavior.
We cannot make the feature positive and add it to the legacy configuration, as
we currently cannot remove features that have already been set in the crosstool
file.
--
MOS_MIGRATED_REVID=104757413
|
|
|
|
|
|
|
|
|
| |
repository.
This is necessary because we copy labels from the command line into tools/defaults/BUILD and currently there is no syntax to make a label in a remote repository refer to one in the main repository.
--
MOS_MIGRATED_REVID=104755206
|
|
|
|
|
|
|
|
|
| |
This CL sure works, but it leaves a few call sites for JavaSemantics#getJavaResourcePath() which make me uncomfortable.
RELNOTES: Java rules now support a resource_strip_prefix attribute that allows the removal of path prefixes from Java resources.
--
MOS_MIGRATED_REVID=104748537
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104708978
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It may be the case that a library used by Java clients is also used
by Android clients, but when used for the latter, it requires a particular
Proguard configuration. This change modifies Java library rules to accept
Proguard specs and pass them up to Android rules.
Note that this does not cause Proguard to be used on normal Java binaries.
RELNOTES[NEW]: java_library now supports the proguard_specs attribute for
passing Proguard configuration up to Android (not Java) binaries.
--
MOS_MIGRATED_REVID=104661799
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104661596
|
|
|
|
|
|
|
|
|
|
|
| |
tools repository.
This is a no-op refactoring CL. The actual switch will be made once everything passes with the new setup.
As a side cleanup, change the awkward realAndroidSdk() / realAndroidCrosstoolTop() mechanism to a converter.
--
MOS_MIGRATED_REVID=104649067
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104529103
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104498435
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104439072
|
|
|
|
|
|
|
| |
it is shadowing.
--
MOS_MIGRATED_REVID=104359435
|
|
|
|
|
|
|
|
|
| |
Previously editing the breakpad contents from a single-architecture binary
to match with the actual app's multi-architecture binary used a Linux-specific
sed flag (-r) which turns out to be unnecessary.
--
MOS_MIGRATED_REVID=104344447
|
|
|
|
|
|
|
| |
These java sources are already included in the idl jars.
--
MOS_MIGRATED_REVID=104309944
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104296834
|
|
|
|
|
|
|
| |
Fixes #404
--
MOS_MIGRATED_REVID=104283324
|
|
|
|
|
|
|
|
|
| |
them to scripts instead of java apps.
RELNOTES: actoolzip, momczip and swiftstdlibtoolzip have all been made into bash scripts and have been renamed to actoolwrapper, momcwrapper and swiftstdlibtoolwrapper respectively. The old versions will be deleted in a later change.
--
MOS_MIGRATED_REVID=104225062
|
|
|
|
|
|
|
|
|
|
| |
This is the new conventions for Copyrights line and some were missed in the previous change.
Generated by:
find -type f -exec sed -i -E 's/Copyright 201([54]) Google Inc/Copyright 201\1 The Bazel Authors/' '{}' ';'
--
MOS_MIGRATED_REVID=104189975
|
|
|
|
|
|
|
| |
objc_libraries.": breaks certain objc_binary build targets.
--
MOS_MIGRATED_REVID=104146276
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104119503
|