| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
RELNOTES[INC]: objc_xcodeproj has been removed, use tulsi.bazel.build instead.
PiperOrigin-RevId: 154829733
|
| |
|
|
|
|
| |
--
PiperOrigin-RevId: 144127414
MOS_MIGRATED_REVID=144127414
|
| |
|
|
|
| |
--
MOS_MIGRATED_REVID=131827507
|
| |
|
|
|
| |
--
MOS_MIGRATED_REVID=131754938
|
| |
|
|
|
|
|
|
|
| |
building watch OS 1 apps.
RELNOTES: Support apple_watch1_extension and apple_watch_extension_binary rules for creating watch OS 1 extensions.
--
MOS_MIGRATED_REVID=119000703
|
| |
|
|
|
|
|
|
|
|
| |
This variable is no longer used because the docgen template directly calls
RuleDocumentationAttribte.getSynopsis() instead of using the SYNOPSIS variable,
and RuleDocumentationAttribute.getHtmlDocumentation() resolves the SYNOPSIS
variable to the empty string.
--
MOS_MIGRATED_REVID=113249993
|
| |
|
|
|
|
|
|
|
| |
Bazel native rule inline documentation.
These variables are no longer used because the docgen templates now directly generate the table of attributes instead of using ATTRIBUTE_DEFINITION and call RuleDocumentation.getAttributeSignature() instead of using ATTRIBUTE_SIGNATURE. RuleDocumentation.getHtmlDocumentation() currently resolves both of these variables to the empty string.
--
MOS_MIGRATED_REVID=112933659
|
| |
|
|
|
|
|
|
|
|
|
| |
of configuration over to the apple package.
This moves a small number of configuration items over. Future changes will mostly likely follow to move yet more items.
The split here is necessary as it is not only objc-related rules which require information about apple platforms and configuration -- cc rules will need this information as well to
pass appropriate args to clang.
--
MOS_MIGRATED_REVID=107396114
|
| |
|
|
|
|
|
|
|
|
|
| |
The headers were modified with
`find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'`
And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan.
The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand.
--
MOS_MIGRATED_REVID=103938715
|
| |
|
|
|
| |
--
MOS_MIGRATED_REVID=103374106
|
| |
|
|
|
|
|
| |
depend on.
--
MOS_MIGRATED_REVID=102763340
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Allows for building and linking to a framework in ios_application
* Currently only works for single arch builds
* Xcode generation produces correct target type, but is mostly untested
The implementation is very similar to that of objc_framework:
1) Build the ios_framework_binary as a dynamic library (-dynamiclib)
2) Symlink the library and public headers to a staging location, inside of "X.framework" bundle. Where X is the name under ios_framework_binary#framework_name
3) Pass the bundle content to ObjcCommon.addFrameworkImports, reusing the core of objc_framework rule implementation. This results in correctly set -F/-framework flags and allows clients to use the framework in a way they would use any SDK/3rd-party framework. It's allowed to import headers via #import <X/X.h> call.
4) Copy the binary and all resources into final application bundle under Frameworks/X.framework
5) Sign the app and nested frameworks
--
MOS_MIGRATED_REVID=100397239
|
| |
|
|
|
|
|
| |
It's not locked down yet as Skylark rules can't declare required fragments.
--
MOS_MIGRATED_REVID=100113647
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reflection, and saves ~15% of initialization time in []RuleClassProvider.create().
Before change:
Over 14 samples,
average = 976
median = 969.9
After change:
Over 14 samples,
average = 811.5
median = 813.9
--
MOS_MIGRATED_REVID=89036261
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this, its first incarnation this rule provides no new functionality - all
it does is take an objc_binary and perform any bundling the objc_binary
would have done anyhow. This will allow us to remove bundling functionality
from objc_binary and add multi-architecture transitions between ios_application
and objc_binary.
However, I did remove the requirement for the infoplist attribute on bundles. We
don't actually need it (a plist is generated automatically) and this removal
makes the transition much easier.
RELNOTES: Introduce ios_application_rule.
--
MOS_MIGRATED_REVID=87194403
|
| |
|
|
|
|
|
|
|
| |
how app extensions are built and how they differ from application bundles.
RELNOTES: Support ios_extension and ios_extension_binary rules for creating iOS app extensions.
--
MOS_MIGRATED_REVID=86788086
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also includes the following changes:
Skylark: tests copy the Skylark files into the same directory. Load statements are replaced with relative paths within bzl files and with absolute paths in tests.
--
Refactor Objc abstract rule classes.
This new arrangement groups attributes by logical purpose and clarifies
rule composition. For example objc_binary inherits "linking" whereas an
objc_library inherits "linkable" but both inherit "compiling".
The only functional change in this CL is to remove the "data" attribute
from all rules as it is not used in the depot and doesn't make sense
when we also allow specifying resources in any number of other ways.
--
MOS_MIGRATED_REVID=86676190
|
| |
|
|
|
|
|
|
|
| |
only links and does not bundle, and creates a binary for an iOS app extension.
ios_extension_binary is minimialistic, not allow infoplist, entitlements, and other attributes, and generate different artifacts, which how objc_binary will also work for iOS applications in the new world when we have ios_application.
--
MOS_MIGRATED_REVID=85728076
|
|
|
--
MOE_MIGRATED_REVID=85702957
|
schmitt
Dmitry Shevchenko
Cal Peyser
Googler
David Chen
Chris Parsons
Damien Martin-Guillerez
Lukacs Berki
Ulf Adams
Matthew DeVore
Han-Wen Nienhuys