1. 08 Jul, 2016 1 commit
    • Drew's avatar
      Update atpkg: · cd8f98bc
      Drew authored
      * bugfix related to automatically importing an external dependency with SSH-based URL
      * link-with => link-with-products
  2. 01 Jul, 2016 2 commits
  3. 30 Jun, 2016 5 commits
    • Drew's avatar
      Merge pull request #109 from AnarchyTools/swiftc-path · dc20b2ad
      Drew authored
      Remove atllbuild option swiftc-path
    • Drew's avatar
      Un-deprecate WMO setting · 3c62219a
      Drew authored
      We can't enable WMO for Release on Linux yet, see https://github.com/AnarchyTools/atbuild/issues/110
    • Drew's avatar
      Add actual effects to the configurations · 8f797026
      Drew authored
      This extends #104 by adding actual effects to the configurations rather than have them be no-ops.
      Effects include:
      * debug instrumentation (new in this PR), for emitting `-g` (see #73 for an obvious extension)
      * optimization control / WMO control
      * compression level (faster debug atbins)
      * test instrumentation (`-enable-testing`)
      * `#if ATBUILD_RELEASE` etc. from Swift code
      There are some deprecations associated with this PR:
      * `whole-module-optimization` atllbuild option is now deprecated; use `--configuration release` instead.  There currently is no plan to control these separately, use `--configuration plain` + `:compileOptions ["-O"]` to get optimization without WMO.  Or open a bug to complain about this change.
      * `magic` atllbuild option is now deprecated; to opt out of magic use `--configuration none` instead.
      Doc PR to follow.
      In addition, CI is now updated to produce release (optimized) builds for atbuild, which significantly optimizes atbuild performance.
    • Drew's avatar
      Remove atllbuild option swiftc-path · 3798f21b
      Drew authored
      This option was deprecated in atbuild 0.9.0.  Use `--toolchain` on the CLI instead.
      Users should have had enough time to migrate at this point.
    • Drew's avatar
      Merge pull request #107 from AnarchyTools/use-atbin · 86a5dffb
      Drew authored
      Add the ability to link with an atbin
  4. 21 Jun, 2016 3 commits
  5. 16 Jun, 2016 1 commit
  6. 15 Jun, 2016 1 commit
  7. 07 Jun, 2016 5 commits
  8. 27 May, 2016 1 commit
  9. 22 May, 2016 1 commit
  10. 21 May, 2016 1 commit
    • Drew's avatar
      Implement configurations · b2ba7bbe
      Drew authored
      This implements, more or less, the scaffolding described in #36.  This commit does not actually make tools behave differently in any configuration (so this is mostly a placebo) but after this, tools can adjust their behavior.
      Notable additions/departures from the original proposal include:
      * Support for "custom" configurations outside the built-in set
      * The addition of `test` and `bench` as built-in configurations, since 2/2 developers use them
      * Internal API has new "helper" methods for common "tool questions" (should we optimize, are we testing, etc.)  Ideally, custom configurations could indicate their own values for these questions, although that's outside the scope of this patch.
      Doc PR to follow.
  11. 18 May, 2016 4 commits
  12. 12 May, 2016 12 commits
  13. 11 May, 2016 3 commits
    • Drew's avatar
      Remove platform hax · 4baf18d7
      Drew authored
      We enabled some hax to get a self-hosted atbuild on 1.1.  However, since 1.2 is released, these hacks are no longer required.
      * Use version field from build.atpkg
      * Use only-platforms to segregate linux/osx packaging behavior
      * Use `package` noptask as an alias for the platform packager
      Resolve #96
    • Drew's avatar
      Merge pull request #97 from AnarchyTools/binpath · d724974a
      Drew authored
    • Drew's avatar
      Add ATBUILD_BIN_PATH · 5e877eb5
      Drew authored
      This adds a new environment variable to point to the bin path.  This is useful for custom tool packagers.
      We also unified the implementation of shell and custom tool environments in the new Shell.environment function.
      There are some minor changes to the custom tool environment that come along with this change, such as running in the directory of the imported package.  To my knowledge, I'm the only one who will notice.