> 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