GEOM must be included, definitely. It enables pythonocc to run the Parametric Application Framework (PAF) which is one of our most important achievement.
SMESH will not be supported in future releases of pythonocc: meshing is a very specific topic, and we do not have enough SMESH knowledge to be able to add value over it. Furthermore, SMESH has dependencies upon boost and fortran, which makes it very difficult to maintain/distribute over different platforms (especially win). As a consequence, Jelle and I think about creating another repository/project dedicated to this subject. Thomas 2011/8/1 Henning Meyer <tutm...@gmail.com> > One remark: I disabled GEOM & SMESH due to ease and missing knowledge about > their importance. > > What's the priority of including both? > Am 01.08.2011 09:58 schrieb "jelle feringa" <jelleferi...@gmail.com>: > > >> > >> Build problem circumvented (was 2.7 related). We now have packages for > >> lucid and maverick (2.6) as well as for natty oneiric (2.7). > >> > > thanks Henning, this work is *much* appreciated! > > have you got any comments / ideas on the following > > matter<http://code.google.com/p/pythonocc/issues/detail?id=37> > > ? > > > > thanks, > > > > -jelle > > _______________________________________________ > Pythonocc-users mailing list > Pythonocc-users@gna.org > https://mail.gna.org/listinfo/pythonocc-users > >
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
