| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146150539
MOS_MIGRATED_REVID=146150539
|
|
|
|
|
|
|
|
|
|
|
| |
that may contain objc source. This only works with dynamic configurations
turned on.
This ensures that objc dependencies of non-objc targets use the apple crosstool.
--
PiperOrigin-RevId: 144384483
MOS_MIGRATED_REVID=144384483
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 143694257
MOS_MIGRATED_REVID=143694257
|
|
|
|
|
|
|
|
|
|
| |
attribute
This prevents duplicate symbol errors for objects that would otherwise be linked both in the application binary and a dylib the binary is linked against.
--
PiperOrigin-RevId: 141478238
MOS_MIGRATED_REVID=141478238
|
|
|
|
|
|
|
|
|
|
|
|
| |
apple_dynamic_library rules
Provided values propagated from "dylib" dependencies will be compiled against the srcs of the rule, and linked together with the dependencies.
It is worth noting that "dylibs" differs from "deps" in that there is no configuration transition along this edge.
There is more work to be done on this attribute, so it remains undocumented. Namely, symbol deduping between dylib and statically-linked dependencies needs to be addressed.
--
MOS_MIGRATED_REVID=137721599
|
|
This is at this point mostly an exercise in refactoring, as this initial
implementation of apple_dynamic_library mirrors apple_binary exactly,
except for the output extension and the -dynamiclib linker arg. There
will be additional followup to deal with significant differences
between these two rules.
--
MOS_MIGRATED_REVID=135822476
|