diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2016-12-16 17:22:28 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2016-12-16 17:22:28 +0200 |
| commit | 75152526696fc024628796f0633ed695d5ebc49c (patch) | |
| tree | faeef54a6b4d7e9a816b8d541500c48484e4ed39 /build2/bin/target.cxx | |
| parent | cc12ed4245a2b61f4c4eb2a970398c920fbc1d37 (diff) | |
Move exe{} to build2 core, add fallback extensions (existing files)
Diffstat (limited to 'build2/bin/target.cxx')
| -rw-r--r-- | build2/bin/target.cxx | 22 |
1 files changed, 0 insertions, 22 deletions
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, |