BIND 10 #1286: C++ code should be built by 'make'

BIND 10 Development do-not-reply at isc.org
Tue Oct 11 00:08:33 UTC 2011


#1286: C++ code should be built by 'make'
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  major         |                       Status:  new
           Component:  build system  |                    Milestone:  Next-
           Sensitive:  0             |  Sprint-Proposed
         Sub-Project:  Core          |                     Keywords:
Estimated Difficulty:  0             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 As a side effect of #1091, we now need to do 'make check' to compile
 C++ test code.  For developers this is very inconvenient; in incremental
 development derived from TDD, we often make small adjustments to the code
 (either the main one or test code) and begin testing by actually compiling
 it (sometimes confirming it does *not* compile is part of test).  Running
 the entire test everytime we do this is a huge overhead.

 We should revert to the previous behavior: just typing 'make' should
 build both the main code and test code.

 I know there was alredy an exception to this behavior in the log module.
 I've not looked into it to see whether it's a mistake or a necessary
 compromise due to (e.g.) dependencies that cannot be resolved easily
 otherwise.  If it's the former, it would be better to fix it at this
 opportunity.

 Note: how to solve this issue is up to whoever takes this task, but it
 would also be nicer if we clarify the use of check_ and noinst_ prefixes
 in Makefile.am.  #1091 introduces many "check_" rules for the purpose of
 not installing test related libraries, but it also caused this side
 effect.
 For consistency, it's better to have a unified usage that achieves both
 - not to install test-only libraries
 - allow test code to be build by 'make' (not requiring 'make check')
 It would aslo be better to be documented in the coding guideline page.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1286>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list