|Message: Re: Geant 4 10.0 linking against system clhep on Mac||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 Thu, 04 Jul 2013 12:49:44 GMT, Mojca Miklavec wrote: > I'm trying to build them with approximately the same reason: to test the > installation (it already turned out that I forgot some dependencies that > would be nice to have, and it certainly helps to verify that samples > don't crash). > > But also someone who is learning Geant4 can start by reading the source > code and running the examples that have already been compiled. Most of > them still allow running additional commands. > > Anyway, I totally agree that samples should never ever be installed to > "bin". > > I wanted to provide an option (not default, but something that the user > would need to activate deliberately) to install examples, compile them > and put the binaries to some nonstandard location. > > But if that's officially "forbidden", I'll try to refrain.
It's certainly not forbidden ;-)! All I'd be concerned about is that you'll end up with unrunnable applications due to the hardcoding of paths to scripts in the applications, and thus inherit a big support burden as the maintainer of the port. There are ways around this hardcoding, but this is low on our priority list at the moment.