Re: [CMake] Compile flag issues and VS Express

2012-02-02 Thread Glenn Coombs
I think 10M is an insanely large default stack size. It just encourages people to create int foo[100][100][100] on the stack instead of learning how to use malloc or new. When creating non-cmake Visual Studio projects the default stack size is way more sensible. I can't see any reason to default

Re: [CMake] Compile flag issues and VS Express

2012-02-01 Thread Yuri Timenkov
I can assume that 10M stack is reasonable for C code, where it's usual to allocate temporary buffers on stack (in C++ it's easier to use heap, e.g. using std::vector). Bad thing is - impact of this flag is detected only at run time. If with /Zm your code just won't compile, with /STACK everything

Re: [CMake] Compile flag issues and VS Express

2012-01-31 Thread Glenn Coombs
On a related note: http://www.gccxml.org/Bug/view.php?id=12437 can you check if ITK and VTK build fine without the large stack size argument (/STACK:1000) as well ? -- Glenn On 30 January 2012 15:58, Bill Lorensen wrote: > ITK and VTK both build fine if I remove the /Zm1000 flag. > > On M

Re: [CMake] Compile flag issues and VS Express

2012-01-30 Thread Bill Lorensen
ITK and VTK both build fine if I remove the /Zm1000 flag. On Mon, Jan 30, 2012 at 10:44 AM, Bill Hoffman wrote: > On 1/28/2012 10:51 AM, David Cole wrote: >> >> Seems reasonable. Is anybody worried that changing the default values >> of these flags would have a negative impact on any projects out

Re: [CMake] Compile flag issues and VS Express

2012-01-30 Thread Bill Hoffman
On 1/28/2012 10:51 AM, David Cole wrote: Seems reasonable. Is anybody worried that changing the default values of these flags would have a negative impact on any projects out there? (i.e. is it likely that anybody relies on these flags being present and that would somehow break their build withou

Re: [CMake] Compile flag issues and VS Express

2012-01-28 Thread Bill Lorensen
Sorry, it was not recent, it was march 2011. On Sat, Jan 28, 2012 at 4:38 PM, Bill Lorensen wrote: > David, > > Someone recently posted a BUG for this: > http://www.gccxml.org/Bug/view.php?id=11913 > > Bill > > On Sat, Jan 28, 2012 at 4:31 PM, Bill Lorensen > wrote: >> I think if you make the

Re: [CMake] Compile flag issues and VS Express

2012-01-28 Thread Bill Lorensen
David, Someone recently posted a BUG for this: http://www.gccxml.org/Bug/view.php?id=11913 Bill On Sat, Jan 28, 2012 at 4:31 PM, Bill Lorensen wrote: > I think if you make the changes specific to VS 2010 they should be OK. > > On Sat, Jan 28, 2012 at 10:51 AM, David Cole wrote: >> On Sat, Jan

Re: [CMake] Compile flag issues and VS Express

2012-01-28 Thread Bill Lorensen
I think if you make the changes specific to VS 2010 they should be OK. On Sat, Jan 28, 2012 at 10:51 AM, David Cole wrote: > On Sat, Jan 28, 2012 at 9:02 AM, Bill Lorensen > wrote: >> Folks, >> >> I'm using VS 2010 Express. >> >> When ever I build a VTK or ITK related app I get errors regarding

Re: [CMake] Compile flag issues and VS Express

2012-01-28 Thread Yuri Timenkov
Don't know about 2010 Express, but IIRC there were problems (at least in previous VS versions) with compiling code with a lot of templates (like spirit, xpressive or MPL from boost). So compiler asks to increase heap size. Anyways, in our projects I always reset CMake's default compile flags: this

Re: [CMake] Compile flag issues and VS Express

2012-01-28 Thread David Cole
On Sat, Jan 28, 2012 at 9:02 AM, Bill Lorensen wrote: > Folks, > > I'm using VS 2010 Express. > > When ever I build a VTK or ITK related app I get errors regarding > virtual memory and warnings about deprecated compiler flags: > use 'EHsc' instead of 'GX' > > I always have to remove the /Zm1000 fl

[CMake] Compile flag issues and VS Express

2012-01-28 Thread Bill Lorensen
Folks, I'm using VS 2010 Express. When ever I build a VTK or ITK related app I get errors regarding virtual memory and warnings about deprecated compiler flags: use 'EHsc' instead of 'GX' I always have to remove the /Zm1000 flag and add the /EHsc flag. I assumed this was do to something screwed