 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello everyone:
I opened project built in vs2008 in source code files to compile it. But i got
some error messages. I defined DISTRIBUTION_MESSAGE_2 in optout.h. There still
some errors like:
1>d:\povray3.6\povwin-3.62\libraries\png\png.h(474) : fatal error C1083: Cannot
open include file: 'zlib.h': No such file or directory
However, the file zlib.h can be found in povwin-3.62\libraries\zlib. So, how
can i fix this problem. By the way, where can i find the document describing the
compile steps.
Thanks!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 10.07.2017 um 16:10 schrieb qingshu:
> Hello everyone:
> I opened project built in vs2008 in source code files to compile it. But i got
> some error messages. I defined DISTRIBUTION_MESSAGE_2 in optout.h. There still
> some errors like:
> 1>d:\povray3.6\povwin-3.62\libraries\png\png.h(474) : fatal error C1083: Cannot
> open include file: 'zlib.h': No such file or directory
>
> However, the file zlib.h can be found in povwin-3.62\libraries\zlib. So, how
> can i fix this problem. By the way, where can i find the document describing the
> compile steps.
From a quick look at the source code package, it seems to me that the VS
2008 project files were poorly maintained. While the `libpng.vcproj` for
VS 2005 lists `..\..\libraries\zlib` as an additional include directory,
the corresponding project for VS 2008 doesn't.
My guess is that the dev team primarily used VS 2005 back then, and only
tested on VS 2008 on rare occasions. An update to libPNG might have
introduced a new dependency on ZLib, which might have gotten fixed in
the VS 2005 libPNG project but forgotten in the one for VS 2008. I
wouldn't be surprised if there were other pitfalls lurking in the VS
2008 project files.
My personal recommendation would therefore be to try and convert the VS
2005 project files to VS 2008 (or use VS 2005 in the first place if you
can get hold of a copy); or, if you have access to a good diff tool and
can find your way around `.vcproj` files in a text editor, try to
synchronize the VS 2008 project files with the VS 2005 ones.
As an entirely different alternative, presuming you're using Windows 10,
you might try Microsoft's "Windows Subsystem for Linux", which is
essentially a Unix-ish command-line environment running on Windows. It
comes with a C/C++ compiler, and since it works fine building (and
running) POV-Ray 3.7 for Unix, chances are it might also work with a
Unix source code package of POV-Ray 3.6. The Unix version does not come
with a GUI though.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> Am 10.07.2017 um 16:10 schrieb qingshu:
> > Hello everyone:
> > I opened project built in vs2008 in source code files to compile it. But i got
> > some error messages. I defined DISTRIBUTION_MESSAGE_2 in optout.h. There still
> > some errors like:
> > 1>d:\povray3.6\povwin-3.62\libraries\png\png.h(474) : fatal error C1083: Cannot
> > open include file: 'zlib.h': No such file or directory
> >
> > However, the file zlib.h can be found in povwin-3.62\libraries\zlib. So, how
> > can i fix this problem. By the way, where can i find the document describing the
> > compile steps.
>
> From a quick look at the source code package, it seems to me that the VS
> 2008 project files were poorly maintained. While the `libpng.vcproj` for
> VS 2005 lists `..\..\libraries\zlib` as an additional include directory,
> the corresponding project for VS 2008 doesn't.
>
> My guess is that the dev team primarily used VS 2005 back then, and only
> tested on VS 2008 on rare occasions. An update to libPNG might have
> introduced a new dependency on ZLib, which might have gotten fixed in
> the VS 2005 libPNG project but forgotten in the one for VS 2008. I
> wouldn't be surprised if there were other pitfalls lurking in the VS
> 2008 project files.
>
> My personal recommendation would therefore be to try and convert the VS
> 2005 project files to VS 2008 (or use VS 2005 in the first place if you
> can get hold of a copy); or, if you have access to a good diff tool and
> can find your way around `.vcproj` files in a text editor, try to
> synchronize the VS 2008 project files with the VS 2005 ones.
>
>
> As an entirely different alternative, presuming you're using Windows 10,
> you might try Microsoft's "Windows Subsystem for Linux", which is
> essentially a Unix-ish command-line environment running on Windows. It
> comes with a C/C++ compiler, and since it works fine building (and
> running) POV-Ray 3.7 for Unix, chances are it might also work with a
> Unix source code package of POV-Ray 3.6. The Unix version does not come
> with a GUI though.
Thank you very much. The project in vs2005 works.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
