Google Git
Sign in
bazel / tulsi / 36052e8daef82669c34f6ed56e39bd300d665f77
commit36052e8daef82669c34f6ed56e39bd300d665f77[log] [tgz]
authornglevin <nglevin@google.com>Tue Feb 20 16:41:11 2018 -0500
committerDavid Goldman <davg@google.com>Thu Feb 22 17:36:03 2018 -0500
treedeaa61209506d195a35bb954ba6ef80601885e06
parent6f202a96d65bef7800a69c301cca4872d05fef42 [diff]
Automated rollback of commit deab940eb7c76a1bb02d912e7014aba27a067541.

*** Reason for rollback ***

Discovered DBGVersion 2 was not using the intended code path, and
furthermore adding this mapping might be causing breakpoints to
fail to resolve when the "dotted path" is present.

This was most noticeable in Xcode 9.3 beta 2, where with this path
and with DBGVersion 2 corrected so that it was mapping to 2 and not
"2", breakpoints were always failing to resolve.

Will consider if another path mapping, perhaps a more traditional one
such as "/normalized/workspace/" or even "/var/root/", works better
than "./".

PiperOrigin-RevId: 186355392
13 files changed
tree: deaa61209506d195a35bb954ba6ef80601885e06
  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.