1. 06 May, 2016 1 commit
  2. 05 May, 2016 1 commit
  3. 26 Apr, 2016 1 commit
  4. 25 Apr, 2016 3 commits
  5. 24 Apr, 2016 5 commits
  6. 22 Apr, 2016 10 commits
  7. 20 Apr, 2016 3 commits
  8. 19 Apr, 2016 1 commit
    • Drew's avatar
      Silence some warnings · 3ad73a90
      Drew authored
      We have overlays that are set automatically by atbuild now, it is
      expected that they won't have an effect across every task.
      3ad73a90
  9. 16 Apr, 2016 1 commit
  10. 15 Apr, 2016 5 commits
  11. 14 Apr, 2016 1 commit
  12. 09 Apr, 2016 1 commit
  13. 07 Apr, 2016 3 commits
    • Drew's avatar
      Use trailing slash for pathOnDisk · 9afedad9
      Drew authored
      This significantly simplifies tools that want to work with paths that
      are relative to the atpkg file.  They can simply use task.importedPath +
      task[field].string! etc.
      9afedad9
    • Drew's avatar
      Implement a substition engine for variable expansion · edafd8e4
      Drew authored
      For many reasons it is desireable to support custom variable expansion
      inside an atpkg file.  This commit does that.
      
      This feature is "opt-in", meaning an individual tool's field must opt in
      to varaible expansion.  This is because:
      
      * Variable substition is not appropriate for all fields and tools
      * The particular expansion I'm PRing here requires a complete parse in
        order to be well-defined.
      
      Here is the syntax:
      
      * `${VARIABLE}` means to substitite for the value `VARIABLE`
      
      * We require two tokens `${` to begin a substition.  This is because `$`
        alone is already in use, and we don't want to immediately break
        compatibility (and CI, etc.)  We reserve the right to deprecate
        unescaped `$` in a future release.
      * We support escape syntax `\${VARIABLE}`
      
      * We also support escape syntax `$?{VARIABLE}` (where `?` is a non-`{`
        character).  We reserve the right to deprecate unescaped `$` in a
        future release.
      
      We also implement the first expansion `${collect_sources:taskname}`.
      This expands to the "collected sources" of the specified task name,
      using the same definition as `atllbuild`.
      
      The intent here is to allow the creation of arbitrary tasks that accept
      source files as arguments.  `xcode-emit` is an obvious candidate, and
      would allow it to break its dependence on atpkg, which it only uses for
      this single feature.
      
      There are other obvious programs that we might want to call with "all
      sources" (e.g. preprocessors, etc.) and they may not want to take a
      dependency on atpkg either.
      edafd8e4
    • Drew's avatar
      Update atbuild to 0.8.2 · 75a694a7
      Drew authored
      75a694a7
  14. 23 Mar, 2016 1 commit
  15. 21 Mar, 2016 3 commits