Google Git
Sign in
bazel / tulsi / c54fe6e6109d65974afb3863798e3bcf14669a42
commitc54fe6e6109d65974afb3863798e3bcf14669a42[log] [tgz]
authordavg <davg@google.com>Wed Feb 14 12:03:51 2018 -0800
committerNicholas <nglevin@google.com>Wed Feb 14 13:03:48 2018 -0800
tree5b123f2fd0096cb1d4af82b612ea767e228f834f
parentf0bab83186b9e474ce2c7fda0e93be838086b3c0 [diff]
Fetch target product-type from AppleBundleInfo

Use the AppleBundleInfo provider if it is present in order to fetch
the product type for the target in Xcode.

PiperOrigin-RevId: 185722935
16 files changed
tree: 5b123f2fd0096cb1d4af82b612ea767e228f834f
  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.