|Message: C++11 standard not being used Geant4-10.01.p02||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)|
I am trying to migrate my application from Geant4-9.04 to Geant4-10.01.p02, so need to move from using GNUmake to CMake. |
I am using the g++4.9 compiler, and have downloaded and built ROOT 6.04.14 with the -Dcxx11=ON flag (I believe it is set by default anyway).
I've then run CMake to generate build scripts for my application with the option -DGEANT4_BUILD_CXXSTD=11. Again, I believe geant4-10.01.p02 sets this by default, but this time I receive a message saying that manually specified variables were not used:
My CMakeCache.txt file nonetheless contains the line:
which seems to suggest that even though my manual specifcation has been ignored, it still uses this option as an uninitialised default.
But still, when I run 'make' I receive error messages suggesting C++11 is not being specified:
I have searched HyperNews and only found one thread documenting a similar issue with 10.01.p01, but the issue should be fixed in the next patch - which I have.
Does this look like a Geant issue? A ROOT issues? Can anyone suggest any measures/checks? Is this fix really in patch 02?
|Inline Depth:||Outline Depth:||Add message:|