From 75152526696fc024628796f0633ed695d5ebc49c Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Fri, 16 Dec 2016 17:22:28 +0200
Subject: Move exe{} to build2 core, add fallback extensions (existing files)

---
 build2/bin/init.cxx   |  3 ---
 build2/bin/target     | 10 ----------
 build2/bin/target.cxx | 22 ----------------------
 3 files changed, 35 deletions(-)

(limited to 'build2/bin')

diff --git a/build2/bin/init.cxx b/build2/bin/init.cxx
index 498118f..ff30c4f 100644
--- a/build2/bin/init.cxx
+++ b/build2/bin/init.cxx
@@ -342,9 +342,6 @@ namespace build2
         t.insert<obja> ();
         t.insert<objs> ();
 
-        t.insert<exe>  ();
-        install_path<exe> (b, dir_path ("bin")); // Install into install.bin.
-
         t.insert<lib>  ();
         t.insert<liba> ();
         t.insert<libs> ();
diff --git a/build2/bin/target b/build2/bin/target
index caf96f4..f3fe4fe 100644
--- a/build2/bin/target
+++ b/build2/bin/target
@@ -60,16 +60,6 @@ namespace build2
       virtual const target_type& dynamic_type () const {return static_type;}
     };
 
-    class exe: public file
-    {
-    public:
-      using file::file;
-
-    public:
-      static const target_type static_type;
-      virtual const target_type& dynamic_type () const {return static_type;}
-    };
-
     // The lib{} target group.
     //
     class liba: public file
diff --git a/build2/bin/target.cxx b/build2/bin/target.cxx
index 770afbb..3277eb1 100644
--- a/build2/bin/target.cxx
+++ b/build2/bin/target.cxx
@@ -129,28 +129,6 @@ namespace build2
       false
     };
 
-    // @@ What extension should we be using when searching for an existing
-    //    exe{}? Say we have a dependency on some pre-existing tool, maybe
-    //    some source code generator. Should we use 'build' extension? But
-    //    what if we find such an executable for something that we need to
-    //    build for 'host'?
-    //
-    //    What if we use extension variables and scoping. We could set the
-    //    root scope exe{*} extension to 'build' and then, say, cxx module
-    //    (or any module that knows how to build exe{}) changes it to the
-    //    'host'. Maybe that's not a bad idea?
-    //
-    const target_type exe::static_type
-    {
-      "exe",
-      &file::static_type,
-      &target_factory<exe>,
-      &target_extension_var<ext_var, nullptr>,
-      nullptr,
-      &search_file,
-      false
-    };
-
     static target*
     liba_factory (const target_type& t,
                   dir_path d,
-- 
cgit v1.1