Re: [Yade-dev] : Compilation on K/Ubuntu 18.04

Hi Klaus, this looks very much like the errors which I have been fixing two months ago. It seems that Robert and Luc were not aware that to compile with CGAL 4.11 we have to use Tri.locate(CGT::Sphere(…)) and when writing ->point() we should instead write ->point().point() (regardless of how

Re: [Yade-dev] Odp: Re: Yade for LTS Ubuntu 18.04

Awesome! Thank you! :-) On 22 Feb 2018, 21:12 +0100, Anton Gladky , wrote: > Dear Yade developers, > > the new minor Yade 2018.02b was released on 20-th of February. > It allows us to compile Yade against CGAL_4.11 and fixes some > bugs. Tarballs are available on GitHub

Re: [Yade-dev] Ip2_FrictMat_FrictMat_FrictPhys doc

When it comes to documentation, for me it’s: never remove anything, always improve :) On 21 Feb 2018, 22:25 +0100, Robert Caulk , wrote: > Hello Jérôme, > > I support clarifying the meaning of particle young in the class reference as > you suggest. There is no doubt that

Re: [Yade-dev] Yade for LTS Ubuntu 18.04

e to get it pushed into Debian->Ubuntu. > > > > > > Regards > > > > > > Anton > > > > > > > > > 2018-02-08 15:23 GMT+01:00 Bruno Chareyre > > > <bruno.chare...@grenoble-inp.fr>: > > > > > > > > > >

Re: [Yade-dev] Yade for LTS Ubuntu 18.04

This is a great effort, I saw you squashed dozens of bugs yesterday. Great! Regarding compiling yade with CGAL 4.11, I can look into it on Saturday, if my last patches didn't work for you? I am currently on a trip and have with me just a small laptop. The last patches I've sent is what I

Re: [Yade-dev] Yade related publication?

Hi Robert, I think that it’s a great idea. Especially if we could use it to directly improve the documentation. I suppose that virtually everything that we could write about using yade could be somehow fit into the sphinx docs. Like in Jerome said, my specific answers to two of your questions

Re: [Yade-dev] Yade with CGAL 4.11

Uh, Bruno :-) I was thinking to ask you whether you have given my diff to Anton after you have modified it. Please do it, or just confirm that the one which I sent is good to go (which isn’t optimal due to too many #ifdefs as you mentioned earlier). best regards Janek On 27 Nov 2017, 20:04