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:  jinmei                     
     Type:  task          |       Status:  reviewing                  
 Priority:  major         |    Milestone:  04. 2nd Incremental Release
Component:  Unclassified  |   Resolution:                             
 Keywords:                |    Sensitive:  0                          
--------------------------+-------------------------------------------------

Comment(by jinmei):

 Replying to [comment:6 each]:

 > > 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

 We can (and probably should) remove --with-boost-lib but cannot --with-
 boost-include, at least right now.  The boost header files under ext are
 incomplete, and since the user may have installed boost (perhaps for a
 different purpose than bind10), if we (us developers mainly) have both the
 incomplete ext version and the full version, the mixture causes trouble.
 It actually happened.

 We should either:

  - Require a full set of boost headers under ext, and always prefer ext to
 other system header files.  With this approach we can remove --with-boost-
 include.
  - Keep the current incomplete version of boost header files under ext,
 but keep --with-boost-include also (for the reason explained above).

 So, this is too early:

 > Went ahead and removed both options, --with-boost-lib and --with-boost-
 include.

 we need to make the decision, then go ahead.

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