|Message: Re: Any advice on wrapping CLHEP into Python||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
> Firstly, is anyone aware of a more extensive wrapping of CLHEP geometric = > primitives than the TwoVector, ThreeVector and Transform3D in the = > existing Geant source tree? It'd be nice to use the operator = > overloading for applying transformations through a simple Python = > multiplication.
I suppose there are no such extensive CLHEP wrapping. I have only warped out classes that are used in Geant4.
But you can easily expose other CLHEP classes you want in the same way as implemented in g4py.
> Secondly, it seems like moving away from bjam towards GNUmake for = > building the extensions is the way to go. > > I can probably get a better handle on this after I spend a few more = > hours walking through the environments/g4py source tree. However, if = > there's anyone out there who's done this already I'd appreciate their = > advice.
Boost are moving from bjam to CMAKE. Bjam is very complicated and not easy to understand and use. Using GNUmake is much easier for handling software building.
I just copied compile options in bjam to GNUmake, that are presented in g4py/sys/XXX.gmk. You can reuse it for building your own wrapper using GNUmake.