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
Component:  Unclassified  |   Resolution:                             
 Keywords:                |    Sensitive:  0                          
--------------------------+-------------------------------------------------

Comment(by each):

 I see the problem.  Using --with-boost-include causes it to omit the "ext"
 directory from its include path, and that's where I put asio.

 This is a little troubling.  The "ext" directory, as I understand it, is
 for external code and headers.  Using a different boost path shouldn't
 cause all the *other* external code to be excluded.

 For that matter, I'm not sure why we allow the user to specify a different
 version of boost.  Is there a good reason for this?  Especially
 considering we're getting rid of the dependency on the boost system
 library, I think maybe we should remove --with-boost-include from
 configure at the same time as we remove --with-boost-system.

 Anyway, I suspect that if you remove that option from configure, it will
 compile.

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