|Message: Re: Dificulty in building 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)|
On Thu, 03 Nov 2016 00:10:43 GMT, Robert Nnaemeka wrote: > Good day all. I successfully installed Geant4 in window 10 using Microsoft visual studio developer command prompt. But after successfully building example B1 and the executable output exampleB1.exe I get the errors telling me I do not have some Geant4 dll files in my computer and asking me to reinstall it. I decided to add the path to the Geant4 dll files directory to the environmental. After doing this, I could no longer even build the example B1. It happens that when I runs > "cmake --build . --config RelWithDebInfo" error is displayed saying that it cannot see some included files the error output is shown below. How can I solve it?
Could you provide a little more detail on the sequence of operations please? What changes to the environment did you make, and did exampleB1 run (i.e. no rebuild) after this change?
On the failing build of exampleB1, does the
Can you run the build again with higher verbosity, i.e. something like:
cmake --build . --config ReleWithDebInfo -- /verbosity:diagnostic
and check the output for the actual compile commands issued, in particular whether there are include paths (
|Inline Depth:||Outline Depth:||Add message:|