|Message: Re: Trouble setting up sim based on example B1||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)|
Thank you for your insight Ivana, it was quite helpful :). I am now running into another odd problem. I have created the Visual studio solution using cmake, however, when I open it in visual studio it does appear to have recognized that there was header files in the folder in which all the source code was taken for building the solution. In this case when I try to build an executable from this I get the following errors:
2> PhilExample1.cc 2>..\geant4_9_5_p02\PhilMonoenergeticModel\PhilExample1.cc(31): fatal error C1083: Cannot open include file: 'PhilDetectorConstruction.hh': No such file or directory 2> PhilDetectorConstruction.cc 2>..\geant4_9_5_p02\PhilMonoenergeticModel\src\PhilDetectorConstruction.cc(31): fatal error C1083: Cannot open include file: 'PhilDetectorConstruction.hh': No such file or directory 2> PhilEventAction.cc 2>..\geant4_9_5_p02\PhilMonoenergeticModel\src\PhilEventAction.cc(31): fatal error C1083: Cannot open include file: 'PhilEventAction.hh': No such file or directory 2> PhilPrimaryGeneratorAction.cc 2>..\geant4_9_5_p02\PhilMonoenergeticModel\src\PhilPrimaryGeneratorAction.cc(31): fatal error C1083: Cannot open include file: 'PhilPrimaryGeneratorAction.hh': No such file or directory 2> PhilRunAction.cc///////////////////////////////////////////////////////////////////////////////
which I assume is because it did not include the header files which I had placed in the source folder for the building of the solution. One thing I did notice was that the header files were written in visual studio C++ and I noticed that they ended with a '.h' whereas the CMakelists.txt which I copied from B1 says to include header files from "include" folder with ".hh". Perhaps this may be a possible cause for why these header files aren't getting included in the solution from the CMAKE building of the visual studio solution. If anyone has any input into this matter it would be greatly appreciated.
I have attached a couple of screen shots, one showing my visual c++ with no include folder on the left hand toolbar where I would expect it to be. And the other is the folder where I saved the header files.
On Thu, 31 Jan 2013 18:06:22 GMT, Ivana Hrivnacova wrote:
> The purpose of the *.in macros is explained in the Applicattion Developers Guide: > http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/ForApplicationDeveloper/html/ch10s02.html > chapter 10.2.2.: > "The exampleBN.in macros are also supposed to be run in a batch mode and their > outputs from the Geant4 system testing are available in the files exampleBN.out." > > The CMake configuration file is defined in such a way that the example can > executed from the build directory, that's the macro files and for convenience > also the .out files are copied from the example source directory here. > In your application, you should customize this block in your CMakeLists.txt: > #---------------------------------------------------------------------------- > # Copy all scripts to the build directory, i.e. the directory in which we > # build B1. This is so that we can run the executable directly because it > # relies on these scripts being in the current working directory. > # > set(EXAMPLEB1_SCRIPTS > exampleB1.in > exampleB1.out > init.mac > init_vis.mac > run1.mac > run2.mac > vis.mac > ) > If you do not want this feature is your application you can simply remove this > code from your CMake file. > > Best regards, >
Attachment: http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2013/01/31/12.16-84548-header_files_included.JPG http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2013/01/31/12.16-54094-saved_header_files.JPG
|Inline Depth:||Outline Depth:||Add message:|