coriolis/crlcore
Jean-Paul Chaput 32cd2304e9 * All Main Python Modules:
- Change: New problem identified with the Python modules: each module seems
        to be built as a complete binary, so all the static C++ initializers are
        allocated in each module. In particular the C++ tree inheritance is built
        for *each* module so we cannot longer uses the typeid() comparisons
        across modules... It was used by boost::program_options to perform is
        casts with boost::any and was starting throwing exceptions because of
        bad casts. program_option was first initialized in "configuration"
        first included by PyViewer then in PyCRL (see Utilities.cpp).
          A first solution is to re-order the import of Python modules in
        stratus1/st_model so that CRL is imported first.
          The second is to not not link "configuration" with boost::program_option
        as only the binary vlsisapd-conf-editor needs it.
          That is a serious problem of which we must be aware and can cause further
        strange behaviors.
          Debug code used to diagnostic has been kept commented in the sources a
        it may be needed again :-(
          This behavior do not affect our singletons because they are part of
        dynamic libraries that seems to be correctly shared between the various
        Python modules.

  * ./crlcore:
    - In PyCRL, module method "getAllianceFramework()" moved as static object
        method "get()" of AllianceFramework. Object AllianceFramework added
        to module CRL.
2010-07-17 10:22:34 +00:00
..
cmake_modules All tools: using the new Goodies macro. 2010-07-13 16:25:20 +00:00
doc * ./crlcore: 2010-06-02 15:52:45 +00:00
etc * ./crlcore: 2010-06-25 08:37:30 +00:00
src * All Main Python Modules: 2010-07-17 10:22:34 +00:00
CMakeLists.txt * All Tools: 2010-07-15 14:00:28 +00:00