Hi Robert, On 1/8/09, Robert Osfield <[email protected]> wrote: > Hi Mattias, > > On Thu, Jan 8, 2009 at 12:04 PM, Mattias Helsing <[email protected]> > wrote: >> I've deleted the cache and started fresh with the above requested >> options. This seems to take a bit of time so you'll have to wait. If >> you want me to digest it somehow just tell me. Otherwise I'll send the >> full zip. > > Just send me the whole zip, I can use nedit to find and sort all the > warnings without much hassle.
I lost the second half, partly thanks to windows clipboard "¤*!#¤"# You got the first 218000 lines of output. The final line count was 469k lines > > I'm curious about the build being slower, is this just because of the > high warning level? I beleive it's the shell IO that suddenly becomes a bottle neck with very verbose output. We used a *very* verbose product a few years ago and couldn't figure out why our app had problems just moving dots until we stopped the verbose output to the console and everything began to run smoothly. Also I forgot to turn on the MP switch after deleting the cache. > > Considering compile is already slow under Windows perhaps it would be > best to avoid the higher level of warnings under Windows once we've > get thing compiling more cleanly at higher warning level. gcc is > already pretty fast so we can probably accommodate a bit more done by > the compiler. I don't think you should opt for a lower warn level ONLY because osg compiles slower in windows. It is only noticable with *many* warnings in which case it doesn't make sense to have a high warning level anyway. Mattias > > Robert. > _______________________________________________ > osg-submissions mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
