POV-Ray: beta: Source Code


POV-Ray : beta : Source Code



		This page provides links to the source code for beta versions of POV-Ray. It also provides instruction on how to build the source, and links to places where discussion of the use of the source may be conducted.



		Building POV-Ray on a UNIX platform requires a relatively modern C++ compiler, the 'make' utility, a Bourne-compatible shell (e.g. bash), and several support libraries. Please refer to the INSTALL file for full details.



		The Linux source code is in povray-3.7.0.beta.34-exp-patched.tar.bz2. The INSTALL file mentioned above is included with the archive. The above archive has been patched to work around the 2009 expiry issue, but is otherwise the same as beta 34. If you wish to get a beta 35a-equivalent build, please download the windows beta 35a source code and extract the 'vfe' and 'source' directories, and substitute those into the linux source tree. This has not been tested by us but should not require major changes.



		Before You Start It may be tempting to just jump in and hit 'Build' with the Visual Studio project. However we can guarantee 100% that this will fail: certain steps are essential for a successful build. This particularly includes setting up the path to the boost headers. See the readme for full details. Compiler The only officially-sanctioned platform for building the current POVWIN source code is a full version of Visual Studio 2005/2008, using the Microsoft compilers. The express edition of VS2005/VS2008 is reported to work, but some workarounds are required if you wish to build the editor provided with the source. (It is not necessary to build the editor to be able to use the EXE). Platform We recommend the use of a 32-bit installation of Windows XP as your host platform for developing with the POVWIN source. Windows 2000 and x64 editions of Windows should also work but have not been tested by us. Either platform can build both 32 and 64-bit versions of POV-Ray. Additional Libraries A copy of the boost libraries for your target platform is required. Details are provided in the readme as to how to obtain a pre-compiled version for targeting win32. Please be aware that we currently only support boost 1.37. Beta Binaries You must have a working version of the latest official beta release installed and running OK before attempting to run your own compile.



		You may download the Windows source from here. The archive contains license information and instructions in a readme.txt and readme.html file. It is essential that you read one of those two files (or the copy stored here) before proceeding. The source will not build unless you follow the steps outlined in that document. The boost archive referred to in the readme is here.



		Currently the officially-sanctioned discussion forum for source-code related issues is the povray.beta-test newsgroup (nntp link). If you intend to refer to an issue within a particular source file, and that file has a revision number available (look for a '$Revision:' field in the comment block at the head of the file), please ensure that you include that number in your post. This makes it easier for developers to refer to the exact version that you have. You should also report the version of the source archive that the file in question came from.



		At this point we would like to emphasize bug fixing/feature completion ahead of adding new and unrelated functionality. If you have found a solution to a bug, we don't even insist that you provide a patch to fix it (though if the fix is significant doing so would help somewhat). Just post in the povray.beta-test forum and provide a description of the bug, a sample scene (if this hasn't already been posted in the group), and your suggested fix. It's important that you tell us why you feel your solution is the correct one for the bug (unless of course it is self-evident, such as a clear coding error on our part). Please be specific as to whether or not you have actually tested your fix. Please also ensure you are specific about the version of the source or of the particular source file you are working with. If you have not mixed files from multiple source archives, then it is sufficient to quote the source release number. Otherwise, please quote the revision number (the "$Revision:" field found in the header of almost all source files) for each source file you refer to in your post. If you do wish to contribute actual code, it will need to be either licensed under a license that does not conflict with the POV-Ray license (e.g. the BSD license), or (more preferably), licensed under our own licenses. In addition, for changes made to certain source files (primarily files that contain code that is either new to version 3.7 or which were re-written for 3.7), we request that you contribute the code under both our license and the GPL3, and allow us to choose which of the two to use. This is to ease our transition to the GPL3 in the future. There are some files already in the source tree which can be re-licensed under this license, and we will not put code into them that is not also re-licensable when the time comes to do it. Those wishing to make significant changes that they would like to contribute to the project may like to post regarding their intentions in the forum (or email us if necessary). Generally, it would be a good idea to let folks know what your are working on, to help avoid possible duplication. If you need to talk directly with a team member regarding the source and can reasonably justify direct-emailing us rather than posting in the newsgroup, you may try sending a mail to `source-37-011 àt povray org`. Please don't write this address down and try it sometime in the future as it probably won't work - by our posting it on a webpage it will eventually get into the hands of spammers, at which point we will delete it and post a new address here.