tulsi
tulsi copied to clipboard
apple_framework is support ?
When I use apple_framework, tulsi generate xcode project is error.
If that is a rule from rules_ios I imagine it would require some changes to support
I meet the same problem
Queuing Tulsi build...
<*> Parsing options completed in 0.112 ms
Running "/Users/mac/.bazel/bin/bazel build --verbose_failures --bes_outerr_buffer_size=0 --apple_platform_type=ios --cpu=ios_x86_64 --watchos_cpus=i386 --announce_rc '--override_repository=tulsi=/Users/mac/Library/Application Support/Tulsi/0.20220209.88/Bazel' --compilation_mode=dbg --define=apple.add_debugger_entitlement=1 --define=apple.propagate_embedded_extra_outputs=1 --define=apple.experimental.tree_artifact_outputs=1 --features=debug_prefix_map_pwd_is_dot --tool_tag=tulsi:bazel_build --build_event_json_file=/Users/mac/Documents/xunlei/FORK/ios-bazel-example/NewApp.xcodeproj/.tulsi/46505_build_events.json --noexperimental_build_event_json_file_path_conversion --aspects @tulsi//:tulsi/tulsi_aspects.bzl%tulsi_outputs_aspect --output_groups=+tulsi_outputs //:NewsApplication", patching output for workspace root at "/Users/mac/Documents/xunlei/FORK/ios-bazel-example" with project path at "/Users/mac/Documents/xunlei/FORK/ios-bazel-example".
note: Options provided by the client:
Inherited 'common' options: --isatty=0 --terminal_columns=80
note: Reading rc options for 'build' from /Users/mac/Documents/xunlei/FORK/ios-bazel-example/.bazelrc:
'build' options: --apple_platform_type=ios --verbose_failures --strategy=SwiftCompile=standalone --apple_generate_dsym
Loading:
Loading: 0 packages loaded
Loading: 0 packages loaded
currently loading:
Analyzing: target //:NewsApplication (1 packages loaded, 0 targets configured)
Analyzing: target //:NewsApplication (37 packages loaded, 167 targets configured)
Analyzing: target //:NewsApplication (37 packages loaded, 167 targets configured)
Analyzing: target //:NewsApplication (38 packages loaded, 167 targets configured)
Analyzing: target //:NewsApplication (38 packages loaded, 167 targets configured)
/Users/mac/Documents/xunlei/FORK/ios-bazel-example/Pods/MBProgressHUD/BUILD.bazel:3:16: error: in @tulsi//:tulsi/tulsi_aspects.bzl%tulsi_outputs_aspect aspect on apple_framework_packaging rule //Pods/MBProgressHUD:MBProgressHUD:
Traceback (most recent call last):
File "/private/var/tmp/_bazel_mac/bc1c6640115027b0e8599f0594bf3ae0/external/tulsi/tulsi/tulsi_aspects.bzl", line 1135, column 39, in _tulsi_outputs_aspect
artifact = bundle_info.archive.path
Error: 'NoneType' value has no field or method 'path'
error: Analysis of aspects '[@tulsi//:tulsi/tulsi_aspects.bzl%tulsi_outputs_aspect] on //:NewsApplication' failed; build aborted: Analysis of target '//Pods/MBProgressHUD:MBProgressHUD' failed
note: Elapsed time: 14.451s
note: 0 processes.
error: Build did NOT complete successfully (78 packages loaded, 2530 targets configured)
<*> Running Bazel completed in 14632.107 ms
/Users/mac/Documents/xunlei/FORK/ios-bazel-example/NewApp.xcodeproj/.tulsi/Scripts/bazel_build.py:590: error: Bazel build failed with exit code 1. Please check the build log in Report Navigator (⌘9) for more information.
<*> Everything completed in 14652.845 ms
Here is My BUILD DETAIL
but bazel build ://xx
success!!!!
If that is a rule from rules_ios I imagine it would require some changes to support
Yeah, using rules_ios apple_framework, However, the Xcode compiler failed to compile, but bazel build can compile properly, do you have any suggestions
Here is My BUILD
Thanks for submitting this issue but this tool is being deprecated. Please checkout rules_xcodeproj for a more complete and maintained Xcode integration.