Google Git
Sign in
bazel / tulsi / 56a071bc4fc31ddb11bbcb5fe9ecce0b591ebba1
commit56a071bc4fc31ddb11bbcb5fe9ecce0b591ebba1[log] [tgz]
authorGoogler <noreply@google.com>Fri Jul 26 20:39:21 2019 +0000
committerIvan Hernandez <ivanhernandez@google.com>Thu Aug 01 23:12:04 2019 +0000
tree43d343247c85d918b3c0879c715763a1a1223520
parent79016be206d6456145ab7c3d87b1cc7801844a5e [diff]
Move bazel_cache_reader to Contents/MacOS/ from Contents/Resources/

Contents/MacOS/ directory is the recommended place for embedded command-line tools:
this is where url(forAuxiliaryExecutable:) looks.

PiperOrigin-RevId: 260204555
4 files changed
tree: 43d343247c85d918b3c0879c715763a1a1223520
  1. .bazelci/
  2. site/
  3. src/
  4. Tulsi.tulsiproj/
  5. .bazelrc
  6. .gitignore
  7. .travis.yml
  8. AUTHORS
  9. BUILD
  10. build_and_run.sh
  11. CODEOWNERS
  12. CONTRIBUTING.md
  13. CONTRIBUTORS
  14. LICENSE
  15. README.md
  16. version.bzl
  17. WORKSPACE
README.md

Tulsi - an Xcode Project Generator For Bazel

Build Status

Building and installing

  1. Run build_and_run.sh. This will install Tulsi.app inside ~/Applications.

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.
  • Tulsi will set some Tulsi-specific flags for bazel invocations, some of which may affect Bazel caching. In order to maximize cache re-use when building from the command line, try using the user_build.py script which is located in the generated xcodeproj at <xcodeproj>/.tulsi/Scripts/user_build.py.

Tulsi project and config settings

Tulsi projects contain a few settings which control various behaviors during project generation and builds.

  • Bazel build flags, customizable per compilation mode (dbg and opt)
  • Bazel build startup flags, also customizable per compilation mode
  • Generation platform configuration: Target platform and arch used during project generation.
    • Can change from targeting iOS sim to iOS device or from iOS to macOS. Setting this improperly shouldn't break your project although it may potentially worsen generation and build performance.
  • Generation compilation mode: Bazel compilation mode (dbg or opt, no fastbuild) used during project generation.
    • Defaults to dbg, swap to opt if you normally build Release builds in Xcode (i.e. profiling your app). Setting this improperly shouldn't break your project although it may potentially worsen generation and build performance.
  • Prioritize Swift: set this to inform Tulsi that it should use Swift-specific flags during project generation.
    • Defaults to No, swap to Yes if your project contains Swift (even in its dependencies). Setting this improperly shouldn't break your project although it may potentially worsen generation and build performance.