Google Git
Sign in
bazel / tulsi / 6ae87dfb0ce5982b0df4ca4541cce7c12a2d3c10
commit6ae87dfb0ce5982b0df4ca4541cce7c12a2d3c10[log] [tgz]
authornglevin <nglevin@google.com>Wed Jan 10 13:18:16 2018 -0500
committerkelvinchan-google <kelvinchan@google.com>Wed Jan 17 17:48:05 2018 -0500
tree99489b9d6994860f658d2dcf38e3fbcae4abeed4
parentd302a01e7bcb9c9fbd460dfffc0d66c2e7170966 [diff]
Added back dotted path remapping.

Allows for LLDB to simulate a relative path in an Xcode-driven debug
session.

PiperOrigin-RevId: 181482482
14 files changed
tree: 99489b9d6994860f658d2dcf38e3fbcae4abeed4
  1. site/
  2. src/
  3. .gitignore
  4. AUTHORS
  5. CONTRIBUTING.md
  6. CONTRIBUTORS
  7. LICENSE.txt
  8. README.md
README.md

Tulsi - an Xcode Project Generator For Bazel

Building and installing

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

  2. 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.