Re: [Opensg-users] OpenSG2: Accumulated changes... part 2: link flags

Hello Marcus and Carsten, First of, we also do need debugging symbols in release builds. Microsoft writes on https://msdn.microsoft.com/en-us/library/windows/desktop/ee416349(v=vs.85).aspx "You also need to take steps to maintain full compiler optimizations while generating symbols." - set

Re: [Opensg-users] OpenSG2: Accumulated changes... part 2: link flags

Hi, We need debugging symbols in release builds. If OPT:REF / OPT:ICF doesn't conflict with /Zi and pdb-generation, I have no objections. Cheers, /Marcus 2017-01-25 0:51 GMT+01:00 Carsten Neumann : > Hello Johannes, > > On 2017-01-18 04:58, Johannes Brunen

Re: [Opensg-users] OpenSG2: Accumulated changes... part 2: link flags

Hello Marcus, I will implement your suggestion and provide a new diff for that. But before I will take the time to build both versions so that I have numbers that I can provide. Please stay tuned, it will take one day or another. Carsten, please wait before check in. I will give it another

Re: [Opensg-users] OpenSG2: Accumulated changes... part 2: link flags

Hi Johannes, Thanks for the explanation! It sounds like /OPT:ICF is safe, even though the debugging experience might be a bit degraded (but not totally). Maybe check and see how much the binary sizes change. If it's only 5-10%, it's not really worth it, but if we gain more than that by COMDAT