commit | 66bf6c51d6e99c3aeba83bce68ea48b8151469df | [log] [tgz] |
---|---|---|
author | nglevin <nglevin@google.com> | Fri Mar 02 17:08:03 2018 -0500 |
committer | Sergio Campama <sergiocampama@gmail.com> | Wed Mar 07 15:11:03 2018 -0500 |
tree | a4fcc0f20291a294a11b0c5e812f2cffd190db8b | |
parent | ea6dbf9335558621a970068fc14538a0e6ce6163 [diff] |
Removed covmap code that hasn't worked since Xcode 7. Following reports that this feature has not worked for Xcode 8, and we are well aware that post_processor has a chance of corrupting binaries, this is absolutely not something we should be keeping in Tulsi. We could look into leveraging LLVM/Clang tooling to address coverage map path remapping, which doesn't seem to work in Swift, but should provide some solutions for (Obj-)C(++) in our projects. PiperOrigin-RevId: 187666858
Open src/Tulsi.xcodeproj, and within Xcode, build the TulsiApp.
Run the TulsiApp.
Tulsi-generated Xcode projects use Bazel to build, not Xcode via xcbuild. This means that many common components of an Xcode project are handled differently than you may be used to. Notable differences: