Google Git
Sign in
bazel / tulsi / fb748fb455e28f4ca3a5905d12633bbb60276db1
commitfb748fb455e28f4ca3a5905d12633bbb60276db1[log] [tgz]
authordavg <davg@google.com>Mon Mar 26 13:51:27 2018 -0400
committerJonathan Dierksen <dierksen@google.com>Wed Mar 28 17:43:12 2018 -0400
treed99962d300647cfaa68c444b17e464532495e895
parentcfa8eba9f73af729e3b2e1d15765ffd11812e273 [diff]
Use rsync to copy over files to Xcode locations

Rsync offers the following advantages:
- Only copy files if they've changed
- Only modify timestamps when files have changed
  - This allows Xcode to more intelligently copy files to device

Note that the artifact_root will only be valid for local builds;
remote builds will need to unzip the IPA or ZIP file.

Also note that currently dynamic frameworks will always be resigned
during an incremental device build; this will cause them to always
be copied over to device even if they have not changed.

PiperOrigin-RevId: 190488842
2 files changed
tree: d99962d300647cfaa68c444b17e464532495e895
  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.