Age | Commit message (Collapse) | Author |
|
This also verifies not passing the required flags keeps the symbols just
in case we change that default accidentally
|
|
This verifies the build and also verifies it actually works which is a
bit nicer
|
|
These are no longer supported with Xcode 14+ which is required for App
Store submissions
|
|
Depends on https://github.com/bazelbuild/bazel/pull/18905 and
https://github.com/bazelbuild/platforms/pull/71
|
|
We don't need this
|
|
This was removed upstream but we still need the smallest possible
transition for testing, this copies the one from rules_apple and removes
a bunch of the features. If this ends up being too much of a pain to
update we'll have to find a different solution.
|
|
If the test/ package is invalid we still shouldn't fail rules_apple.
This can happen when bazel deletes an API that we use only in tests in
this repo
|
|
No reason to complicate the shell tests with generating this test rule
|
|
|
|
This is a useful test rule copied from rules_apple stripped down to only
what we need right now. This will allow us to remove some of our shell
tests, and write starlark tests instead of shell tests in the future.
|
|
Since we went a different route in rules_swift and require the -ObjC
flag to be disabled there too, this isn't as necessary. This reduces the
risk of people making new reliance on -ObjC and when other changes land
to flip the default on this we won't have to worry about that case.
|
|
This extracts the -ObjC flag into a separate crosstool feature, and
makes it apply to all CC linking actions. Previously this only applied
to objc-executable actions, but as this gets unified into the cc linking
behavior it makes sense to apply it to the cc actions as well. This has
the potential downside that if you had a cc_binary target that had
Objective-C in the dependency tree that it did not use, previously it
would not have been loaded and now it would. If that becomes a problem
this flag can be removed on thew binary in question by disabling this
feature. This also allows us to remove this flag from rules_swift's
logic since it was there for the same reason.
|
|
|
|
This makes it easy to test a few different configurations
|
|
This allows us to call this from non-shell tests and avoids some shell
test complexity
|
|
|
|
This allows more generic flags to be passed that need to use the
execroot. This makes it easier for users to pass things like this
without requiring crosstool modifications
|
|
This migrates the Apple CC toolchain from bazel into this repo. This
allows this to evolve and be updated without a full bazel udpate.
Bazel's built in unix toolchain can still be used to build macOS C++
targets, but this repo handles a wider variety of Apple specific flags
and requires you have Xcode installed.
|
|
RELNOTES: None
PiperOrigin-RevId: 480103119
(cherry picked from commit fb7ab89d22dbe25f5022707db8892eb5bcac2858)
|
|
- This avoids the need for a `sh_binary` to be built specific to macOS.
- Make the script minimal to the support needed.
- Since there is no label/name passed in, derive the name for the script based
on the output file.
RELNOTES: None
PiperOrigin-RevId: 447731982
(cherry picked from commit 62eb11cfa7a97b5380391ad9b765b21fbbbb9d35)
|
|
|
|
|
|
The `lib` directory is for Starlark modules.
|
|
|
|
This is basically a copy of the new `apple_universal_binary` rule but
with a simpler interface (there are no `minimum_os_version` and
`platform_type` attributes), and the output binary is forced to be
multi-arch. This rule is meant to be used for host/exec tools so that
they are built as universal binaries regardless the architecture of the
execution platform.
Co-authored-by: Keith Smiley <keithbsmiley@gmail.com>
|
|
|
|
RELNOTES: None
PiperOrigin-RevId: 365833288
(cherry picked from commit aa71415a4d277e071e278f2d7edf6b679bbfc60b)
|
|
RELNOTES: None
PiperOrigin-RevId: 364986436
(cherry picked from commit feaae213cb6a5af28f83a7ac550d70acc680e5a4)
|
|
RELNOTES: apple_support.path_placeholders.platform_frameworks() no longer accepts a ctx argument.
PiperOrigin-RevId: 364873873
(cherry picked from commit 9c175c7f47c476006491be5dce510a15f05067df)
|
|
|
|
RELNOTES: None
PiperOrigin-RevId: 321657656
|
|
on the availability of the selected Xcode.
This is part of a series of changes that set the execution requirements for actions generated by rules that require Xcodes. The dynamic scheduler will later be modified to run those actions locally/remotely accordingly, but this does not currently change behavior.
RELNOTES: None.
PiperOrigin-RevId: 287338096
|
|
It was a mix of a funcions/constants, this way they all are functions,
hopefully making it easier to use (via consistency).
RELNOTES: apple_support.path_placeholders.sdkroot & apple_support.path_placeholders.xcode are both functions now.
PiperOrigin-RevId: 230407105
|
|
Avoiding https://github.com/bazelbuild/bazel/issues/7180
RELNOTES: None
PiperOrigin-RevId: 229942617
|
|
Adds tests for xcode_support and apple_genrule.
RELNOTES: Added xcode_support.bzl, which includes support methods for managing Xcode configurations.
PiperOrigin-RevId: 229415609
|
|
RELNOTES: None
PiperOrigin-RevId: 227878199
|
|
RELNOTES: None
PiperOrigin-RevId: 224646998
|