Add ability to specify ad hoc recipe actions

We are reusing the buildspec syntax for that.

1 files changed, 0 insertions, 70 deletions

diff --git a/libbuild2/spec.hxx b/libbuild2/spec.hxx
deleted file mode 100644
index d2ed609..0000000
--- a/libbuild2/spec.hxx
+++ /dev/null
@@ -1,70 +0,0 @@
-// file      : libbuild2/spec.hxx -*- C++ -*-
-// license   : MIT; see accompanying LICENSE file
-
-#ifndef LIBBUILD2_SPEC_HXX
-#define LIBBUILD2_SPEC_HXX
-
-#include <libbuild2/types.hxx>
-#include <libbuild2/forward.hxx>
-#include <libbuild2/utility.hxx>
-
-#include <libbuild2/variable.hxx>
-
-#include <libbuild2/export.hxx>
-
-namespace build2
-{
-  struct targetspec
-  {
-    using name_type = build2::name;
-
-    explicit
-    targetspec (name_type n): name (move (n)) {}
-    targetspec (dir_path sb, name_type n)
-        : src_base (move (sb)), name (move (n)) {}
-
-    dir_path src_base;
-    name_type name;
-
-    // The rest is calculated and cached.
-    //
-    scope* root_scope = nullptr;
-    dir_path out_base;
-    path buildfile; // Empty if implied.
-    bool forwarded = false;
-  };
-
-  struct opspec: vector<targetspec>
-  {
-    opspec () = default;
-    opspec (string n): name (move (n)) {}
-
-    string name;
-    values params;
-  };
-
-  struct metaopspec: vector<opspec>
-  {
-    metaopspec () = default;
-    metaopspec (string n): name (move (n)) {}
-
-    string name;
-    values params;
-  };
-
-  using buildspec = vector<metaopspec>;
-
-  LIBBUILD2_SYMEXPORT ostream&
-  operator<< (ostream&, const targetspec&);
-
-  LIBBUILD2_SYMEXPORT ostream&
-  operator<< (ostream&, const opspec&);
-
-  LIBBUILD2_SYMEXPORT ostream&
-  operator<< (ostream&, const metaopspec&);
-
-  LIBBUILD2_SYMEXPORT ostream&
-  operator<< (ostream&, const buildspec&);
-}
-
-#endif // LIBBUILD2_SPEC_HXX