Folks,

I'd appreciate it if someone with VS2005 installed could take a stab at 
building the project in http://www.povray.org/temp/povwin_s_3.62.zip. 
The VS2005 project in that archive has been hand-converted from VS2008 
format but not directly tested as I don't have a copy of that version of 
VS handy at the moment.

Also anyone who wishes to do a test build with VS2008 is welcome to do so.

NB no instructions are (yet) included with the archive. However there's 
nothing particularly different about building it vs prior versions (it 
should be a case of just filling in the DISTRIBUTION_MESSAGE_2 macro and 
hitting build).

thanks,

-- Chris

Post a reply to this message

Results so far:

- The 'libpng' subproject needs to have the include path to zlib added.
- The debug configuration creates a 'cmedit32d.dll' but the actual debug  
executable looks for 'cmedit32.dll'. It does however use 'povcmax32d.dll'.

After overcoming those two obstacles, and copying 'povray.ini' to the  
location where POV-Ray now expects to find it, I could run the demo render  
without any noticeable issues with both debug and SSE2 configurations.

Tested with VS2005 and Boost 1.38.0.


-- 
FE

Post a reply to this message

> I'd appreciate it if someone with VS2005 installed could take a stab

I tried it with C++ 2005 Express & Platform SDK. In this environment
it is hard to build the editor DLLs. Is it intentional that their build
is now enabled by default? Also, the project dependencies in the
solution properties were set so that povwin depended on the
cmedit and codemax project, causing the link to fail because
this implies a dependency of povcmax32(d).lib.

Furthermore, I added

   comctl32.lib gdi32.lib user32.lib kernel32.lib
   advapi32.lib shell32.lib

to the additional linker dependencies of povwin (I think the
normal version of Visual Studio links these by default but
having them in the project can't hurt).

After that (and fixing the zlib include for libpng) all
configurations compiled fine.

Finally, the project could define _CRT_SECURE_NO_DEPRECATE to suppress
the flood of deprecation warnings as use of the old style functions
would seem to be intentional anyway.

> The VS2005 project in that archive has been hand-converted from VS2008 
> format but not directly tested as I don't have a copy of that version of 
> VS handy at the moment.

Sounds like a somewhat painful way of maintaining two project versions.
Note that Visual Studio 2005 and 2008 can coexist peacefully on the same
system. You could also install C++ Express 2005 just for editing the
project files - and some day the platform SDK to test the build ;)

Post a reply to this message

Christian Froeschlin wrote:

> You could also install C++ Express 2005 just for editing the
> project files - and some day the platform SDK to test the build ;)

Come to think of it, in this scenario you probably already have a
platform sdk (or Windows SDK) which came with VS 2008 and you might
only need to point there.

Post a reply to this message

Christian Froeschlin wrote:
> Sounds like a somewhat painful way of maintaining two project versions.
> Note that Visual Studio 2005 and 2008 can coexist peacefully on the same
> system. You could also install C++ Express 2005 just for editing the
> project files - and some day the platform SDK to test the build ;)

I'm travelling and only have my laptop, and don't really have room for 
full parallel installs. I do have that setup at home.

If you would like to contribute a working VS2005 project with all the 
listed problems fixed please feel free to email it to me and I'll 
include it in the release (and probably re-import the VS2008 project 
from it).

Also anyone who wants to write a 'how to build' readme is invited to do 
so, sometimes it's better to get this done from the perspective of 
someone who hasn't spent the past 15 years hacking on the source;)

thanks,

-- Chris

Post a reply to this message

> If you would like to contribute a working VS2005 project with all the 
> listed problems fixed please feel free to email it to me and I'll 
> include it in the release (and probably re-import the VS2008 project 
> from it).

I sent you my adapted versions of the project files by mail.

Post a reply to this message

Christian Froeschlin wrote:
>> If you would like to contribute a working VS2005 project with all the 
>> listed problems fixed please feel free to email it to me and I'll 
>> include it in the release (and probably re-import the VS2008 project 
>> from it).
> 
> I sent you my adapted versions of the project files by mail.

Got it, thanks ... I've updated the source archive - please double-check 
and if it's OK I can probably release it.

-- Chris

Post a reply to this message

Chris Cason wrote:
> Christian Froeschlin wrote:
>>> If you would like to contribute a working VS2005 project with all the 
>>> listed problems fixed please feel free to email it to me and I'll 
>>> include it in the release (and probably re-import the VS2008 project 
>>> from it).
>>
>> I sent you my adapted versions of the project files by mail.
> 
> Got it, thanks ... I've updated the source archive - please double-check 
> and if it's OK I can probably release it.

Sorry for the delay I've been away for some time.

I just downloaded the updates source archive and it seems to include
the zlib include fix for libpng but *not* the modified dependencies
in povray.sln and and *not* the additional linker dependencies in
povwin.vcproj.

If you wish to reapply them it is probably best if you change
the settings directly on your side:

1. In project properties for povwin, select "All Configurations",
    and under Linker > Input set Additional Dependencies to:

comctl32.lib gdi32.lib user32.lib kernel32.lib advapi32.lib shell32.lib

2. In the solution properties, under

      Common Properties > Project Dependencies

    Select project povwin and uncheck the boxes next to
    the dependencies codemax and cmedit.

3. In the solution properties, under

      Configuration Properties > Configuration

    select "All Configurations" and uncheck the "build"
    boxes for codemax and cmedit.

Post a reply to this message

Thanks for the followup. I've updated the source, would you mind 
checking it again?

regards,

-- Chris

Post a reply to this message

Chris Cason wrote:

> Thanks for the followup. I've updated the source, would you mind 
> checking it again?

You had me confused with including an *older* version of povray.sln
compared to the previous archive but I think you replaced it with the
version I sent you earlier ;)

I tested 32-bit debug, release and release SSE2 in C++ Express 2005
and all three configurations built out of the box. I don't have
C++ Express 2008 so these files are untested.

I noticed belatedly that the build options are also specific to
the platform: only Win32 is currently modified. I don't see these
configurations in the GUI as I don't have a 64-bit Windows. I think
it is possible to build 64-bit binaries with c++ express after
installing the appropriate SKD, but I suppose the first user who
wants to do this will just have to figure it out on his own ;)

Post a reply to this message