yade-users team mailing list archive
-
yade-users team
-
Mailing list archive
-
Message #09173
Re: [Question #245682]: optional compilation of LBM engine
Question #245682 on Yade changed:
https://answers.launchpad.net/yade/+question/245682
Status: Open => Answered
Anton Gladky proposed the following answer:
Please, commit your changes, I will try to fix it
just after that.
Anton
2014-03-18 19:01 GMT+01:00 Luc Sibille <question245682@xxxxxxxxxxxxxxxxxxxxx>:
> Question #245682 on Yade changed:
> https://answers.launchpad.net/yade/+question/245682
>
> Status: Answered => Open
>
> Luc Sibille is still having a problem:
> Using
> ADD_DEFINITIONS("-DLBM_ENGINE")
> did not change anything.
>
> Now I have additionnal informations during the compilation, i.e. at make step (with the option -DCMAKE_VERBOSE_MAKEFILE=1 (by the way I don't now why but these additionnals informations are not displayed at each compilation...), and there is something strange. At make step there is:
> -- Yade configured with following features: Eigen3 VTK OpenMP GTS GUI CGAL PFVflow GL2PS
> -- Disabled features: Odeint LinSolv LBMFLOW
> thus LBM engine is disable whereas at cmake step there is:
> -- Yade configured with following features: Eigen3 VTK OpenMP GTS GUI CGAL PFVflow GL2PS LBMFLOW
> -- Disabled features: Odeint LinSolv
> and we expect the LBM engine to be enable.
>
> Here are the two lines the CMakeCache.txt relative to the LBM engine:
> //Enable LBM engine (very experimental)
> ENABLE_LBMFLOW:BOOL=OFF
> there is nothing else about LBM...
>
> I tried also to define ENABLE_LBMFLOW=ON by default with:
> OPTION(ENABLE_LBMFLOW "Enable LBM engine (very experimental)" ${DEFAULT})
> as it is done for instance for the PFV engine, but there is still
> ENABLE_LBMFLOW:BOOL=OFF in CMakeCache.txt
>
> ... oh, actually:
> ENABLE_LBMFLOW:BOOL=OFF in CMakeCache.txt in the "build" directory
> but
> ENABLE_LBMFLOW:BOOL=ON in CMakeCache.txt in the "trunk" directory
> thus, why CMakeCache.txt is not updated in the "build" directory? Should I rebuild the whole code as for a very new installation of Yade? How can I impose to rebuild the whole code as for a new installation?
>
> Luc
>
> You received this question notification because you are a member of
> yade-users, which is an answer contact for Yade.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-users
> Post to : yade-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-users
> More help : https://help.launchpad.net/ListHelp
--
You received this question notification because you are a member of
yade-users, which is an answer contact for Yade.