BIND 10 #168: separate ASIO from Boost and remove custom code

[BIND 10 Development]

#168: separate ASIO from Boost and remove custom code
--------------------------+-------------------------------------------------
 Reporter:  larissas      |        Owner:  each                                       
     Type:  task          |       Status:  reviewing                                  
 Priority:  major         |    Milestone:  04. 2nd Incremental Release: Early Adopters
Component:  Unclassified  |   Resolution:                                             
 Keywords:                |    Sensitive:  0                                          
--------------------------+-------------------------------------------------

Comment(by each):

 > Please also make sure the intermediate UNUSED_PARAM hack will be removed
 from the ASIO code.

 Done in r1951.

 And in r1952, I put in pragmas to suppress the unused parameter warnings
 in the two places that had them (asio_link.cc and lib/cc/session.cc -- I
 considered making a separate asio_session.cc, but it already seems to be
 fairly well abstracted as it is).

 I have also moved ext/asio and ext/boost down a level to ext/asio/asio and
 ext/boost/boost.  This enables us to continue using the top-level "ext"
 directory for externally provided header files, but switch the groups on
 or off selectively.  Building with ext/asio doesn't force us to include
 ext/boost, and changing the boost include directory has no effect on
 ext/asio.

 Compiles fine for me, but your build environment seems to be touchier than
 mine... can you try it out?

-- 
Ticket URL: <https://bind10.isc.org/ticket/168#comment:15>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development