commit	e343790d11bbcb386460eac8a3604c122d1e6c9d	[log] [tgz]
author	nglevin <nglevin@google.com>	Wed Mar 28 17:59:43 2018 -0400
committer	kelvinchan-google <kelvinchan@google.com>	Thu Apr 05 17:43:14 2018 -0400
tree	ebcf599f6815e49b18d483aa418f927624783628
parent	206fb046722ca07a3f2062315a1ed9db6f5b8bcc [diff]

Added common debug path normalization support.

Requires a wrapped_clang and CROSSTOOL update before this will be
enabled. Right now this is overridden with a
TULSI_DIRECT_DBG_PREFIX_MAP flag.

Currently debug path normalization requires the following:

1) There is no Swift. Swift debug info cannot be normalized with
the Swift compiler, swiftc. This could be possible in a future
version of Swift.

2) Post processor (for Xcode < 9) isn't being used to patch dSYM.

3) TULSI_DIRECT_DBG_PREFIX_MAP isn't enabled.

Removed the extra path mapping feature, as it is not necessary for
path normalization, and will not work well with lldbinit based
debugging as it was written.

This change also allows Swift debugging support WITHOUT dSYMs, for
faster builds, on Xcode 9 and above.

PiperOrigin-RevId: 190839630

25 files changed

tree: ebcf599f6815e49b18d483aa418f927624783628

README.md

Tulsi - an Xcode Project Generator For Bazel

Building and installing

Open src/Tulsi.xcodeproj, and within Xcode, build the TulsiApp.
Run the TulsiApp.

Notes

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:

BUILD files are the source of truth; most changes made to your Xcode project won't affect the build.
- Adding new sources to the Xcode project won't include them in your app; they must be added to BUILD files.
- Changes made to your BUILD files, such as adding new library dependencies, are incorporated automatically when building your generated project. The only time you need to re-run Tulsi is if you want to add additional build targets or have new source files show up in Xcode for editing.
- The Info.plist file is governed entirely by BUILD rules in Bazel and is not displayed in the Xcode UI.
- Changes to compilation flags (i.e. -DHELLO) should be made in the BUILD files in order to affect the build; changes made to compilation settings in the Xcode UI will only affect indexing. You may want to regenerate your project using Tulsi after modifying compilation flags.