|Message: Re: geant4-config program||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)|
On Mon, 12 Oct 2009 10:39:30 GMT, Guy Barrand wrote: > Hi > > It could be fine to arrange to have a "geant4-config" program available (in the bin directory) after a G4 build and installation had been done. > > This is needed for people that want to build a G4 app but by not using the G4 make system.
This is a "work in progress" at the moment! I hope to have a beta version, if not a fully working version, by the end of the year. This partly ties in with work on a new build system for Geant4, though 'geant4-config' will appear before this.
> One painful point with G4 is that G4 can be installed with or without "global / granular" libs > (which is unique ! I don't know another software having two "lib flavors") > and with the includes "gathered in one include directory" or not. And this various cases definitely complicate the life of people in their build system to detect the various G4 installation cases.
You've identified the major issue with writing this script cleanly :-)! It can be made to work I think, with some care.
> I would suggest then that G4 comes with a "geant4-config" programs that provides the "right infos" > at least for : > geant4-config --cflags (or --incs) > geant4-config --libs > > And then up to the geant-config program to look how G4 had been installed and then to return > the correct infos. For exa for "--libs" to return the "granular flavor" is the global libs are not here. > The "global flavor" if the granulars are not here. And probably the globals if both are here (because > the list of the globals is shorter). > And about the "--incs" then returns the "-I
This is pretty much the algorithm I'm working to, though there are also "--granular-libs" and "--global-libs" options if both are available and the user specifically wants one or the other. There is also a "--has-
> (Not so clear if the --incs, --libs should return the CLHEP infos. Probably not since CLHEP already > comes with a clhep-config). > > (There is the entry 1218 of O.Lahaye that looks similar to this post, but not clear to me if the "pkg-config" mentioned here is the same than "having a geant-config". Then I prefer to have an explicit > entry for this issue).
These are partly related - if you're building a Geant4 application you shouldn't need to know that CLHEP is required, or for that matter, any of the other potential dependencies. The pkg-config tool has the functionality to take care of this, though not of Geant4's dependencies provide a pkg-config file (AFAIK).
I'm gradually learning about how to deal with the external dependencies, and it doesn't seem to be a trivial problem across all supported platforms. It will be solvable I'm sure, just needs some time and care!
|Inline Depth:||Outline Depth:||Add message:|