From 5579832b31a8a2dcf3d30f1ce2669cf9015afd0d Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Thu, 9 Aug 2018 16:37:33 +0200
Subject: Remove explicit extension specification

Now build2 is able to deal with it automatically.
---
 buildfile | 11 +++--------
 1 file changed, 3 insertions(+), 8 deletions(-)

diff --git a/buildfile b/buildfile
index d4f8627..36f963e 100644
--- a/buildfile
+++ b/buildfile
@@ -8,16 +8,11 @@ vcpkg/
   {
     ./: vcpkg/exe{vcpkg} file{VERSION.txt}
 
-    # @@ Specify extensions explicitly because of source file names like
-    # commands.edit.cpp. Failed that, we will end up treating, in this case
-    # .edit, as a specified extension (because the pattern machinery will
-    # remove .cpp from matches that it has added to the pattern).
-    #
     # Note that we need the explicit fsdir{} because our distribution won't
-    # have this directory.
+    # have this (empty) directory.
     #
-    vcpkg/exe{vcpkg}: cxx{src/vcpkg/**.cpp   +src/vcpkg}   \
-                      hxx{include/vcpkg/**.h +include/pch} \
+    vcpkg/exe{vcpkg}: cxx{src/vcpkg/**     +src/vcpkg}   \
+                      hxx{include/vcpkg/** +include/pch} \
                       fsdir{vcpkg/}
 
     cxx.poptions =+ "-I$src_base/include" -DDISABLE_METRICS=1 \
-- 
cgit v1.1