Hi Lionel,
regarding my try to build QxOrm with MinGW I proposed to change the build structure of QxOrm to make it easier to maintain. Now I managed to build QxOrm with MinGW and restructured the build system of QxOrm. I uploaded my proposal here: http://www.cetoni.de/QxOrm_MinGW.zip.
I used the same build layout like Qt or QtCreator. That means there is no separation between source and headers. Each supdirectory contains a *.pri file with all sources and headers and includes the pri files of the sub directories. Then I changed the included paths in all files. Because I added the main src folder as include folder I can use include paths relative to this include folder. So instead of writing includes like #include "../../../include/QxSerialize/boost/QxSerializeInclude.h" it is now possible to write #include "QxSerialize/boost/QxSerializeInclude.h".
When I compiled QxOrm I stumbled across another problem. I use boost 1.43 and the build process of QxOrm failed because of a lot of compiler errors of this kind:
include/QxSerialize/Qt/QxSerialize_QPoint.h:42: error: conflicting declaration 'mpl_assertion_in_line_42'
include/QxSerialize/Qt/QxSerialize_QColor.h:42: error: 'mpl_assertion_in_line_42' has a previous declaration as '<anonymous enum> mpl_assertion_in_line_42'
I googled a little bit and found that this is a bug in BOOST_CLASS_VERSION macro in boost 1.43:
http://permalink.gmane.org/gmane.comp.lib.boost.user/59865
So you should use another boost version or replace the version.hpp file in boost/serialization folder with a new version from boost trunk where this problem is fixed.
After these changes and after I fixed the boost 1.43 issue I could sucessfully compile QxOrm with MinGW 4.4.0.
I have not run the test cases yet so I cant't confirm the functionality but at least I can compile QxOrm now.
What do you thing about the proposed QxOrm build structure?
Uwe