Thi Doan
Thi Doan
It's a bit confusing but Tulsi needs Bazel 5.0+ to build (which I think you have already built it with a pre-release of Bazel 6.0), but [Mediapipe needs Bazel 4.2.1](https://github.com/google/mediapipe/blob/e6c19885c6d3c6f410c730952aeed2852790d306/.bazelversion#L1),...
We've just updated Tulsi with the new Apple rules releases. Can you try again with the latest commit? (You will need Bazel 4.0.0 to build it now.)
You mean the pre-processed ones? You can add them via the `additionalFilePaths` in your tulsigen.
Add the path to that file to your tulsigen file, for example: https://github.com/bazelbuild/tulsi/blob/c7609aa3914123f1b5f1a6b5caff551617a325c9/Tulsi.tulsiproj/Configs/Tulsi.tulsigen#L32-L34
I thought this is an Xcode 12 regression. I’ve filed a radar about it.
The workaround is to generate a focused project, by editing your `.tulsigen`'s `sourceFilters` to only include what you want to see in the generated project.
~There's a workaround to make code completion and highlighting work: build the indexing target once (the build doesn't need to be success).~ Update: It doesn't seem to work in all...
It seems to be because of custom Swift compiler flags, because Tulsi doesn't expand the Make variables correctly. You can remove all flags in **Other Swift Flags** from the generated...
Yes, it worked for me. Did you remove it from the indexing target? (the framework target starts with `_idx_`)
I think it would still works if you build from Xcode since you aren't supposed to build the indexing target (though I'm not sure how it would affect the indexing...