POV-Ray : Newsgroups : povray.programming : Compiling Pov-Ray and a suggestion: : Re: Compiling Pov-Ray and a suggestion: Server Time
3 Jul 2024 06:21:33 EDT (-0400)
  Re: Compiling Pov-Ray and a suggestion:  
From: Severi Salminen
Date: 21 Jan 2004 06:20:39
Message: <400e6087$1@news.povray.org>
ABX wrote:

> On Wed, 21 Jan 2004 12:46:43 +0200, Severi Salminen
> <sev### [at] NOT_THISsibafi> wrote:
> 
>>2. Since speed is of essence and some people just want to change (say) 
>>the Windows editor, it would be a nice option, if the editor and the 
>>POV-Ray engine itself could be compiled separately as not everyone can 
>>use the fastest compilers. Speed differences in editor usually don't 
>>matter at all.
> 
> Note POV-Ray for Windows is threaded application with prorities for threads
> and "Duty Cycles" so you can adjust time your CPU use for rendering. And you
> can not use editor at all and use only Queue feature for rendering scenes
> taken from other editors. And you still have possibility to create custom
> config.h and compile core source without GUI with your Intel C++. Creation of
> config.h should be simple from technical point of view ;-)

I think I was not clear enough. I meant that there might be people, who 
want to make changes to the source code of the _editor_ (not the engine) 
and compile it and use it - without losing the optimizations of the 
engine itself. This is possible only if they have the Intel Compiler. 
Now they allways have to compile the engine together with the editor and 
the rendering speed might suffer if they don't have the Intel Compiler. 
If the editor could be separated, there would be no such issues.

Severi Salminen.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.