On Wed, 13 Feb 2008 10:06:07 +0100, Chris Cason  
<del### [at] deletethistoopovrayorg> wrote:
> Frederik

Hmpf!



Some preliminary remarks:

Building the editor dlls requires that you have the ATL libraries and  
headers installed. They are included in the default installation options  
of VC2k5, but can be deselected. Not a big deal, but worth mentioning in  
the build instructions.

Using the 'DEVELOPMENT' macro to make POV-Ray search for the editor dlls  
in the 'codemax' directory (as described in the readme) does not work,  
because it looks for them in the wrong place. POV-Ray looks for  
'"..\\codemax\\" BINDIRNAME "\\" EDITDLLNAME', but it should be  
'"..\\..\\codemax\\" BINDIRNAME "\\" EDITDLLNAME'.

The linker fails to link in the debug info in 'vc80.pdb' because it is not  
in the same directory as 'povcore-debug.lib' (one is in 'Win32 Debug', the  
other in 'bin32'). I have not yet investigated what impact this has on  
debugging.


Compilation produced no errors though, and the resulting executable seems  
to work fine. I have not attempted to add OpenEXR yet.


-- 
FE

Post a reply to this message

Chris,

I sent you an email reply outlining my results.  Let me know if you don't get it.

Kyle

Post a reply to this message

On Wed, 13 Feb 2008 22:49:19 +0100, "Fredrik Eriksson" <fe79}--at--{yahoo}--dot--{com>
wrote:


>Building the editor dlls requires that you have the ATL libraries and  
>headers installed. They are included in the default installation options  
>of VC2k5, but can be deselected. Not a big deal, but worth mentioning in  
>the build instructions.

As a side note, the ATL libraries and headers are not included in VC++ 2005 Express
Edition.  The
header files are in the Windows platform SDK, but the atlthunk.lib library isn't.  I
found a
workaround that seems to have worked here...

http://www.codeproject.com/KB/wtl/WTLExpress.aspx

Post a reply to this message

Kyle <hob### [at] gatenet> wrote:
> Chris,
>
> I sent you an email reply outlining my results.  Let me know if you don't get it.
>
> Kyle

I've done the same.

Tom

Post a reply to this message

Fredrik Eriksson wrote:
> Using the 'DEVELOPMENT' macro to make POV-Ray search for the editor dlls  
> in the 'codemax' directory (as described in the readme) does not work,  
> because it looks for them in the wrong place. POV-Ray looks for  
> '"..\\codemax\\" BINDIRNAME "\\" EDITDLLNAME', but it should be  
> '"..\\..\\codemax\\" BINDIRNAME "\\" EDITDLLNAME'.

strange ... it works here (I built from the same zip you used, loaded the
EXE, then used process explorer to confirm that the local copy of the DLL's
was loaded). note that visual studio (at least, VS 2005) sets the working
directory to that of the project, rather than that containing the EXE.

if you add the '/debug' switch to the command-line options in the project
settings, and then run pvengine, you should get a c:\povdebug.txt file,
containing something like the following:

  CWD is d:\Temp\povwin-src-3.7\windows\vs 2005

What does your one give?

-- Chris

Post a reply to this message

On Thu, 14 Feb 2008 12:02:17 +0100, Chris Cason  
<del### [at] deletethistoopovrayorg> wrote:
> strange ... it works here (I built from the same zip you used, loaded the
> EXE, then used process explorer to confirm that the local copy of the  
> DLL's
> was loaded). note that visual studio (at least, VS 2005) sets the working
> directory to that of the project, rather than that containing the EXE.

That explains it. I was running pvengine.exe directly from the 'bin32'  
directory.

Another thing I noticed:
Since the executable name and path is identical for all configurations  
(Debug, Release and SSE2), it is rather cumbersome to switch between them.  
It would be preferable to have separate names and/or paths.


-- 
FE

Post a reply to this message

On Thu, 14 Feb 2008 13:00:06 +0100, Fredrik Eriksson  
<fe79}--at--{yahoo}--dot--{com> wrote:
> Another thing I noticed:
> Since the executable name and path is identical for all configurations  
> (Debug, Release and SSE2), it is rather cumbersome to switch between  
> them. It would be preferable to have separate names and/or paths.

I just noticed that the SSE2 executable did indeed have a different name,  
but I think the debug version should too.


-- 
FE

Post a reply to this message

Fredrik Eriksson wrote:
> On Thu, 14 Feb 2008 12:02:17 +0100, Chris Cason  
> <del### [at] deletethistoopovrayorg> wrote:
>> strange ... it works here (I built from the same zip you used, loaded the
>> EXE, then used process explorer to confirm that the local copy of the  
>> DLL's
>> was loaded). note that visual studio (at least, VS 2005) sets the working
>> directory to that of the project, rather than that containing the EXE.
> 
> That explains it. I was running pvengine.exe directly from the 'bin32'  
> directory.

ah, I see. the macro is really intended for use when running from the IDE,
particularly if you want to debug the editor code itself.

I really ought to clean the whole project layout up - I've done it for the
version 3.6 project but that was after I did the 3.7 branch. all the
project files should be in the VS 2005 directory, and the DLL's should end
up in the bin32 directory, rather than where they are now.

> Since the executable name and path is identical for all configurations  
> (Debug, Release and SSE2), it is rather cumbersome to switch between them.  
> It would be preferable to have separate names and/or paths.

this is intentional - probably a reflection of the way I tend to develop, I
found the standard Visual Studio habit of separating the EXE's into their
own dir was a hassle, as I'm constantly switching between various builds,
and I simply want my various shortcuts (desktop, objectdock, keyboard
launchpad) to always point at the EXE I most recently built. back when I
had them separate, I too many times ran a multi-hour test render only to
find that I'd launched the wrong EXE :-(

thanks for the feedback anyhow. I have added an additional check for the
codemax DLL's in ..\..\ as well as ..\.

-- Chris

Post a reply to this message

Tom York wrote:
> Kyle <hob### [at] gatenet> wrote:
>> Chris,
>>
>> I sent you an email reply outlining my results.  Let me know if you don't get it.
>>
>> Kyle
> 
> I've done the same.

Got both, thanks.

-- Chris

Post a reply to this message

Thanks to Tom, Kyle and and Fredrik for their assistance - it resulted in
some significant changes and improvements to the presentation of the source
and its readme.txt.

The source is now available - please see the announcement in this group.

-- Chris

Post a reply to this message