Re: [Cppqed-support] cmake build system

[Andras V. <and...@ui...>]

Dear Raimar,

I have merged, pushed, and updated the documentation. I have also
merged part of the new composite architecture, so that now there is a
fine-grained control on the system characteristics of BinarySystem.
The same is under preparation for Composite.

> To make the documentation consistent we should also merge the cmake branch
> into BoostIntegration and BlitzCVS_compatibility. For the latter the cmake
> files have to be adjusted a little bit to remove all the serialization stuff and
> to detect the old cvs version of blitz++. I will do this once you have merged
> the cmake branch into the main branch.

I think in the BoostIntegration branch it is also necessary to remove
the enable-binary-output option because in this branch we assume that
the Boost dependency is header-only and furthermore the necessary
headers are included in the distribution.

Best regards,
András



>
> Best regards
> Raimar
>
> On Saturday 04 August 2012 00:49:00 Raimar Sandner wrote:
> > Dear András,
> >
> > I have pushed my first attempts with the cmake build system, and it works
> > quite well (dependency checking, library detection). Could you please test
> > the branch raimar/cmake?
> >
> > At the top level source directory, the steps are:
> >
> > mkdir build && cd build
> > cmake -DCMAKE_BUILD_TYPE=<type> ..
> >
> > where <type> is release or debug (unfortunately this is a bit clumsy).
> >
> > and then there are several options, e.g.
> >
> > make -j4
> > make -j4 VERBOSE=1
> > make -j4 1particle1mode
> > make -j4 fewer_scripts
> >
> > At the moment cmake checks for the required stuff (boost, blitz++, gsl,
> > gslcblas) and fails if one of these is not found. It also checks the
> > optional flens, boost-serialization and blitz++ with serialization support
> > and enables the corresponding features if these are found. If not, a
> > message is printed but the configuration succeeds. I would have to check if
> > it is possible to override the optional features and to disable them even
> > if they are detected (if this is desired?). If we are lucky this just works
> > out of the box for MacOS, I will test it next week.
> >
> > Best regards
> > Raimar
> >
> > ----------------------------------------------------------------------------
> > -- Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Cppqed-support mailing list
> > Cpp...@li...
> > https://lists.sourceforge.net/lists/listinfo/cppqed-support
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Cppqed-support mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppqed-support