2009/8/11 Thomas Paviot <tpav...@gmail.com> > 2009/8/11 Sébastien Ramage <sebastien.ram...@gmail.com> > > >> >> Thomas Paviot a écrit : >> >> >>> I compiled he latest svn rev. from the SalomeGeometry repository. The >>>> modified headers are only used to generate SWIG files. It's possible you >>>> need to recompile SalomeGeometry. >>>> >>>> >> I don't understand why you have changed the name of header files? for >> example your SGEOM_Application.hxx is the same as GEOM_Application.hxx. >> What change did you make in SalomeGeometry source ? >> > > Because the SalomeGeometry GEOM package conflicts with the OpenCASCADE Geom > package. Under Linux, it's not a problem. But under Windows, it's not > possible to make any difference between GEOM.hxx and Geom.hxx. > > I then just renamed all GEOM_*.hxx to SGEOM_*.hxx (and also modified the > headers that include GEOM_*.hxx). > > As a consequence: > from OCC.Geom import * #imports the Geom package from OpenCASCADE library > from OCC.SGEOM import * #imports the SalomeGeometry GEOM package > > It's the only change I made to the headers. I did not modify the C++ source > files. > > But I must also say that the naming conventions used in the GEOM Salome > package are quite confusing: GEOM, GEOMImpl, GEOMAlgo, Archimede etc. Is > there any consistency in these module names? What do they mean? I had a long > discussion with Fotis (author of the SalomeGeometry project) about this > topic. He will do the same as we already did for pythonOCC: > - keep a SalomeGeometry that is synchronous with the Salome project. I > mean, it's just a 'copy' of the Salome files, > - provide additional headers, with a different grouping/hierarchy, so that > it's much more convenient and easier to deal with this library. > > >> >> Sébastien >> > BTW, any better idea is welcome!
> > Thomas > >
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
