Blame doc/FAQ

Packit 8c9aa0
Frequently Asked Questions:
Packit 8c9aa0
---------------------------
Packit 8c9aa0
Packit 8c9aa0
1) Questions relating to CppUnit
Packit 8c9aa0
   ----------------------------
Packit 8c9aa0
Packit 8c9aa0
1.1) Isn't there an easier way to write unit tests than using TestCaller ?
Packit 8c9aa0
Packit 8c9aa0
   Yes, there is. Macros have been created to take care of the repetitive 
Packit 8c9aa0
work. Look up include/extensions/HelperMacros.h in CppUnit documentation. 
Packit 8c9aa0
Most of CppUnit test suite is also written that way since they remain 
Packit 8c9aa0
compatible as CppUnit evolve.
Packit 8c9aa0
Packit 8c9aa0
Packit 8c9aa0
2) Questions related to Microsoft Visual VC++
Packit 8c9aa0
   -----------------------------------------
Packit 8c9aa0
Packit 8c9aa0
2.1) Why does the compiler report an error when linking with CppUnit library?
Packit 8c9aa0
Packit 8c9aa0
   You most likely are not using the same C-RunTime library as CppUnit.
Packit 8c9aa0
   In Release configuration, CppUnit use "Mulithreaded DLL".
Packit 8c9aa0
   In Debug configurations, CppUnit use "Debug Multihreaded DLL".
Packit 8c9aa0
   Check that Projects/Settings.../C++/Code Generation is indeed using
Packit 8c9aa0
the correct library.
Packit 8c9aa0
   
Packit 8c9aa0
2.2) Why does CppUnit generate warning 4786:... when compiling ?
Packit 8c9aa0
Packit 8c9aa0
   I really don't have a clue. All CppUnit's headers starts by either
Packit 8c9aa0
including Portability.h or another CppUnit's header. Portability.h includes
Packit 8c9aa0
config-msvc6.h which disable that specific warning. The warning is generated
Packit 8c9aa0
by TestFactoryRegistry::m_factories. A solution to this problem is welcome.