-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use Crashlytics #425
Comments
Just to confirm do you have these bazelrc flags set? |
We're using C++17 standard because it is needed for other projects we have, but otherwise yes. I also tried just now with C++14, and still get the same errors. |
I am adding this Crashlytics example to try and reproduce your error. |
Thanks @cgrindel ! I can clone a branch and test too if/when you have one up. Also amending my original issue, I actually am now receiving the same errors whether or not I specify |
Quick update. I found one issue where a modulemap target is being added as a dep though one is unnecessary. To fix this, I need to refactor some source inspection code to occur earlier in the repository processing. I plan to put up a 2-3 pull requests. The first 1-2 will be the refactor. The final one will be the fix for the modulemap dep logic. |
- Add `label` to target. - Add `pkginfo_targets.get_by_label()`. - Pass `repository_ctx` to `pkginfos.new_from_parsed_json()`. - Add `swift_src_info` with `has_objv_directive`. - Add `testutils` module. - Update tests to use mangled repository name when retrieve `repository_ctx.name`. Related to #425.
- Move `swift.FileInfo` to `swiftpkg.SwiftFileInfo`. - Update `swiftpkg.SwiftFileInfo` to check for `@objc` directive. - Add `ModulemapLabel` to `swift.Module`. For Swift source modules, this field is populated if a modulemap target is required (e.g., has `@objc` directives). - Add `modulemap_label` to `deps_indexes.new_module`. - Update `deps_indexes.labels_for_module` to check for `modulemap_label` on the module instead of assuming that all Swift targets that are a dependency for an Objc target should have one. Related to #425.
- Treat `maccatalyst` like `ios` instead of `macos`. - Add `crashlytics` example to `firebase_example`. - Ensure that `defines` values that contain spaces are escaped properly. If not escaped, each space-separated part becomes its own define value. - Do not trust the package manifests! Check that directories exist before attempting to list their contents. - Include `.mm` files (Objective-C++) as valid sources. Closes #425.
Including Firebase Crashlytics fails with the following:
Package.swift:
BUILD.bazel:
If I add--apple_platform_type=ios
to the build flags (which AFAIK I shouldn't need to do, because my build target is an ios_application), I only get the LoggerLevel errors:The text was updated successfully, but these errors were encountered: