31 | | * ''--enable-ecut'' - says that the !TestRunner, comprising all unit tests in one exectuable, shall make use of the Eclipse !CppUnitTest (ECUT). If this is started within eclipse with this plugin instanlled, a shiny interface will tell you what failed and what not. |
| 31 | * ''--enable-ecut'' - says that the !TestRunner, comprising all unit tests in one exectuable, shall make use of the Eclipse !CppUnitTest (ECUT). If this is started within eclipse with this plugin installed, a shiny interface will tell you what failed and what not. |
| 32 | |
| 33 | A note about ''configure'': If one library is found only under some specific path, you can add CFLAGS, CPPFLAGS, LDFLAGS, ... to the configure call, like this |
| 34 | {{{ |
| 35 | ../configure --prefix=`pwd` --enable-hydrogen CFLAGS="-Wall -g3" CXXFLAGS="-Wall -g3" |
| 36 | }}} |
| 37 | which enables all compiler warnings and full debugging of the code without any optimization. ''configure'' saves these variables, too, such that when it is called to re-configure it will still make use of them from its cache file. |
| 38 | |
| 39 | There are several flags that change the way molecuilder is compiled and probably make it run faster, more unsafe, ... |
| 40 | || FLAG || what it does || |
| 41 | || -DLOG_OBSERVER || What the Observers do is logged, the log is printed on exit || |
| 42 | || -DNO_MEMDEBUG || !MemDebug (memory debugger) is disabled || |
| 43 | || -DNO_CACHING || Cachable are short-wired, i.e. always recalculate, this slows down the code a lot || |
| 44 | || -DNDEBUG || include NO_MEMDEBUG, also ASSERTs are not checked, this speeds up the code by a factor of 5 || |