Google Git
Sign in
bazel / tulsi / 03914cc6d6fbc8351d7960b6a0dd239bc2b541f9
commit03914cc6d6fbc8351d7960b6a0dd239bc2b541f9[log] [tgz]
authornglevin <nglevin@google.com>Tue Apr 03 13:01:10 2018 -0400
committerkelvinchan-google <kelvinchan@google.com>Thu Apr 05 17:43:44 2018 -0400
treeeacaaebe862c6ffa6598227745ae6998c590e713
parent5278fe9c98a3ffbc3e8972f9d2bea35be01dcb6d [diff]
Bootstrap LLDBInit on project generation.

This presents an opportunity for us to update ~/.lldbinit or
~/.lldbinit-Xcode so that it can locate ~/.lldbinit-tulsiproj so that
it can do path remappings when they are needed for builds without
dSYM bundles.

Still, Xcode requires that it loads ~/.lldbinit or ~/.lldbinit-Xcode
when Xcode itself launches, otherwise it will never be able to
relocate ~/.lldbinit-tulsiproj until the next time Xcode is
restarted.

This could be further improved by generating a prompt for command
line and GUI to request that users restart Xcode after project
generation completes, although that will have to be addressed
alongside other changes and improvements to the Tulsi GUI.

PiperOrigin-RevId: 191456351
6 files changed
tree: eacaaebe862c6ffa6598227745ae6998c590e713
  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.