RE: [boost] BOOST TEST and strict /Za - can theMSlanugageextensions option be enabled in a program

From: Paul A. Bristow (boost_at_[hidden])
Date: 2003-09-12 09:17:48

| -----Original Message-----
| From: boost-bounces_at_[hidden]
| [mailto:boost-bounces_at_[hidden]]On Behalf Of Ehsan Akhgari
| Sent: Friday, September 05, 2003 4:04 PM
| To: 'Boost mailing list'
| Subject: RE: [boost] BOOST TEST and strict /Za - can
| theMSlanugageextensions option be enabled in a program
|
|
|
| I don't get what is so bad about a static library.  It can be built and
| later injected into projects using:
|
|  #pragma comment( lib, "library_name.lib" )
|
| The only thing that needs to be done is copying that library to the
| compiler's lib directory at library build time, which can be automated
| by using an "install" makefile option or something, like the Regex++
| library does.
|
|
| -------------
| Ehsan Akhgari
|

This seems most convenient, for example requiring just:

#pragma comment( lib, "unit_test_library.lib" )

and

#include <boost/test/unit_test.hpp>   // for unit_test framework

in the test file,

and setting the 'global' library directory using

Tools, Options, Projects, VC++ Directories, drop-down selecting library instead
of executables, and adding a new item

J:\Cpp\Unit_test_library\Debug

or

J:\Cpp\Unit_test_library\Release

However perhaps you can advise how to make this work to select the right library
for release and debug modes.

J:\Cpp\Unit_test_library\$(ConfigurationName) doesn't appear to work in this
context in release mode. (Lots of duplicate libc. ... at link stage).

Thanks

Paul A Bristow, Prizet Farmhouse, Kendal, Cumbria, LA8 8AB  UK
[phone]   Mobile [phone]
mailto:pbristow_at_[hidden]