1. 22 Apr, 2016 1 commit
  2. 07 Apr, 2016 2 commits
    • Drew's avatar
      Allow variable expansion for shell tool · 409cc69b
      Drew authored
      This allows the execution of a shell tool with the "collected sources"
      of another task.
      
      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.
      
      See https://github.com/AnarchyTools/atpkg/pull/23
      409cc69b
    • Drew's avatar
      Update to atpkg/master · ac691a13
      Drew authored
      Bootstrap
      ac691a13
  3. 02 Feb, 2016 1 commit
    • Drew's avatar
      Update atpkg · 7b3eccc4
      Drew authored
      We need a new bootstrap as well
      7b3eccc4
  4. 17 Jan, 2016 2 commits
    • Drew's avatar
      Update OSX bootstrap phase · 9b8fccd9
      Drew authored
      9b8fccd9
    • Drew's avatar
      Support for importing remote tasks from another file · 7f624456
      Drew authored
      We have to be careful about how these paths work; because when you
      import a new file it is as if your working directory changes.  To
      support this, we add a new `importedPath` property to Task that contains
      the path where the task is imported (whether local or remote).  This
      property is documented to include a trailing slash to avoid various
      problems involving relative paths.
      
      We also fix #20 by moving to `collectSources` implemented in atpkg
      instead of atllbuild.
      7f624456
  5. 16 Jan, 2016 1 commit
    • Drew's avatar
      Restore bootstrap · 932df14e
      Drew authored
      Okay, I understand the desire to do this, but we can't.  Not yet.  Open
      an issue.
      
      The behavior we need is that we don't have to manually muck around with
      the bootstrap files when we organize the repository.  We can actually
      generate them from a (working) atbuild, check them into source control,
      and then bootstrap can use them without any atbuild installed.
      
      The catch is, they need to talk to the .atllbuild directory, not some
      other .bootstrap directory.
      
      To get the latter behavior, open an issue and I can add support for this
      in atllbuild.
      
      This commit restores the behavior where we can generate the bootstrap
      files from a working atbuild again, so we don't have to edit them by
      hand.
      932df14e