Thi Doan
Thi Doan
> Xcodes should fail gracefully if xcodeSelectPrintPath fails. I think it should not fail though. If I have a new Mac, the first thing I download would be `xcodes`, and...
The error might be misleading and not the actual one—`ios_application` should be supported. Can you provide a minimal reproducible example (that has a `.tulsiproj`)?
You can add it to your WORKSPACE and run it with Bazel. ``` bazel run @build_bazel_tulsi//:tulsi -- -- [flags] ````
Are you hardcoding the path to your module map file like `-fmodule-map-file=external/path/to/module.modulemap`? If the path is expanded by Bazel then it will be mapped by Tulsi to be something like...
(I shouldn't have used the word "map".) In the generated Xcode project's "Other Swift Flags" setting, the module map flags become `-Xcc -fmodule-map-file=$(TULSI_BWRS)/external/path/to/module.modulemap` (Tulsi prepends `$(TULSI_BWRS)/` to the file path)....
Would adding mapping for `external` to target.source-map work? Something like: ``` settings set target.source-map "./external/" "/path/to/main/repo/bazel-repo/external/" settings append target.source-map "./" "/path/to/main/repo/" ```
I think this is the convention for Apple frameworks--headers are flattened into the `Headers` and `PrivateHeaders` directories in the final framework.
Oops, I think I was misunderstanding your issue. `ios_static_framework` does not support bundling private headers.
@ravimandala Friendly ping—any update? :)
Can you sign a CLA?