|Message: Re: Compilation issues on Windows 10 using Visual Studio 2015||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 got the similar problem when install G4.10.02 on Win7 with VS2015. Did you solve your problem with VS2010? I can still see some "warning LNK4221" in your attached file.
On Sat, 23 Apr 2016 23:19:59 GMT, Youming Yang wrote:
> HI all, > > As a sanity check, compilation of G4 10.01p03 using VS2010 (C++98 > standard) compiled successfully. Output attached. > > The compilation of the same code on VS2015 (c++98 standard also) failed > as I mentioned originally. Again this issue seemed to stem from lines of > code in xmlparse.cc: > > 18>C:\geant\geant4_10_01_p03\source\externals\expat\src\xmlparse.cc(1912): > error C3688: invalid literal suffix 'L'; literal operator or literal > operator template 'operator ""L' not found > > Which I'm guessing does not play well with some internal changes between > the c++98 implemetnations VS2010 and VS2015. > > If there is a portable, robust way to modify the code in xmlparse.cc to > allow VS2015 compilation I'd be grateful to hear it. > > Also, I use windows and Visual studio strictly for debugging, and > perform data runs on Linux clusters (which also is why my original issue > of compiling 10.02 on VS2015 in debug mode with too many debug symbols > is also a deal breaker). > > thank you all again, Ming > > Attachment: > http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2016/04/23/15.52-30348-2010.txt >
|Inline Depth:||Outline Depth:||Add message:|