Re: [boost] Formal review: New Boost.Test Library + Jam

From: Beman Dawes (bdawes_at_[hidden])
Date: 2001-12-12 17:19:59

I'm trying to review the Test library.  One of the activities I tried was 
to build the library using Boost.Jam.

To do so, I added a Jamfile (adapted from regex) to libs/test/build:

subproject libs/test/build ;

SOURCES = execution_monitor.cpp test_tools.cpp unit_test_config.cpp 
unit_test_log.cpp unit_test_main.cpp unit_test_monitor.cpp 
unit_test_result.cpp unit_test_suite.cpp ;

lib libboost_test$(SUFLIB) : ../src/$(SOURCES)
     :
         <include>$(BOOST_ROOT)
     :
         debug release
     ;

dll libboost_test$(SUFDLL[1]) : ../src/$(SOURCES)
     :
         <include>$(BOOST_ROOT)
     :
         debug release
     ;

I also added "subinclude libs/test/build ;" to the main Jamfile.

First, is this the correct approach?  (It sort of worked, but there are 
code porting issues confusing things.  I've sent those to Gennadiy.)

Minor point: shouldn't the "/" characters be $(SLASH) so they work on a 
wider variety of operating systems, for example.

Second, I think we need a rule that library submissions requiring builds 
should always be accompanied by appropriate Jamfiles.  Without a known-good 
Jamfile, it is very hard to quickly check for code portability.

Comments?

--Beman