 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Is there any person who had sucesfully compiled povray and/or mega pov for
windows with free line commands tools from Borland Museum ? I'm tired of working
with djgpp version in console window and I'm looking for a way to achive own
legal compilation of windows version. Only free for windows is Borland C++
Compiler 5.5 but without tasm and with ilink instead tlink.
And BTW: http://www.openwatcom.org/info.html - I hope it will be free for all
platforms.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wlodzimierz ABX Skiba wrote:
>
> Is there any person who had sucesfully compiled povray and/or mega pov for
> windows with free line commands tools from Borland Museum ? I'm tired of working
> with djgpp version in console window and I'm looking for a way to achive own
> legal compilation of windows version. Only free for windows is Borland C++
> Compiler 5.5 but without tasm and with ilink instead tlink.
>
> And BTW: http://www.openwatcom.org/info.html - I hope it will be free for all
> platforms.
>
> ABX
Yes, I've. Couple of tips:
both POVRay and Borland have file mem.h (Borland includes this file in
standard header file memory.h) and this creates number of problems. I've
avoided it by copying borland's mem.h to mem1.h and changing Borland's
memory.h to use mem1.h. After this you have to ensure, that POV-Ray's
include files are in include path before Borland ones (makefile should
take care of it).
I'll post makefile and configuration file for Borland compiler for
MegaPOV in povray.binaries.programming. Take official source release for
Windows, install it and copy these files over official ones (offical one
has old version, number of files is changed/removed) in
POVRAY/windows/borland directory (POVRAY designates installation
directory). (if new version does not have borland directory, then just
create it under windows directory and copy these files there. I've used
version from 3rd IRTC CD). Then copy MegaPOV source files over POV-Ray
files and invoke make from borland command environment in
POVRAY/windows/borland directory. It should do it. (if your borland
installation is not in default directory c:\borland\bcc55, then change
this path in makefile). This makefile contains lots of crap, but it
worked for me...
If you try other makefiles, then be sure, that it defines
COMMONCTRL_VERSION, otherwise you have number of compile problems with
files in Windows directory. I used following C option:
-DCOMMONCTRL_VERSION=0x0400 (this is defined in above mentioned
makefile).
Warning: I'm afraid, that free version comes without optimizer: I've
tried to compile with and without optimization and there is no
difference, result is still much slower than VC++ version. So for
release You want probably to compile with other compiler.
This is all, I hope: I've done this some times ago, so it is possible,
that I've forgot something. If this does not work, then drop note and I
try to recall, what else I did.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Vahur Krouverk wrote in message <3ADC73B0.2D96A0AB@aetec.ee>...
> Wlodzimierz ABX Skiba wrote:
> > Is there any person who had sucesfully compiled povray and/or mega pov for
> > windows with free line commands tools from Borland Museum ?
>
> Yes, I've. Couple of tips:
Thanks for your help. I did it !
> both POVRay and Borland have file mem.h (Borland includes this file in
> standard header file memory.h) and this creates number of problems.
My problem was strange message: "_WIN32_IE setting conflicts with _WIN32_WINNT
setting" announced at begining of prsht.h - but after your suggestion with
renamed mem.h it disappeared.
> I'll post makefile and configuration file for Borland compiler for
> MegaPOV in povray.binaries.programming.
Your makefile is for standard povray not for megapov but there is no problem for
me to generate proper makefile for megapov of for my own compilation of pov
> This makefile contains lots of crap, but it
> worked for me...
it needs additional parameter for linker -P32 becouse default page size is to
small
> Warning: I'm afraid, that free version comes without optimizer: I've
> tried to compile with and without optimization and there is no
> difference, result is still much slower than VC++ version.
Have you installed both service packs on your bcc55 ?
> So for
> release You want probably to compile with other compiler.
Djgpp has possibility to compile binaries for windows but I never tested it.
Djgpp has omptimizations as every gcc based compiler and perhaps there is gate
to open-free-legal world :-)
Little more at http://www.delorie.com/djgpp/v2faq/faq3_6.html
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wlodzimierz ABX Skiba wrote:
>
> Thanks for your help. I did it !
Made POV-Ray? Good!
> Your makefile is for standard povray not for megapov but there is no problem for
> me to generate proper makefile for megapov of for my own compilation of pov
>
Oops, my mistake. This is apparently older version of makefile, before
modifying it for megapov.
> > Warning: I'm afraid, that free version comes without optimizer: I've
> > tried to compile with and without optimization and there is no
> > difference, result is still much slower than VC++ version.
>
> Have you installed both service packs on your bcc55 ?
Don't know, perhaps not. Someone dl-ded it from Borland and I just
unpacked it in my computer.
Do You have both? How fast is rendering (e.g. of skyvase) with regard to
MS VC++ version?
I already thought, that I'll collect money and buy MS VC++ for
development (standard edition does not have optimizer, so I considered
Professional Edition), but its quite expensive; if Borland's free
version can do optimizing, then I'll go with it.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Vahur Krouverk wrote in message <3ADDA2D6.6D31706A@aetec.ee>...
> Wlodzimierz ABX Skiba wrote:
> > Thanks for your help. I did it !
> Made POV-Ray? Good!
just own compilation, not whole POV-Ray ;-)
> > Have you installed both service packs on your bcc55 ?
>
> Do You have both?
yes
> How fast is rendering (e.g. of skyvase) with regard to MS VC++ version?
here are results:
OFFICIAL (optimized for pentium 2)
Peak memory used: 1148079 bytes
Time For Parse: 0 hours 0 minutes 2.0 seconds (2 seconds)
Time For Trace: 0 hours 4 minutes 53.0 seconds (293 seconds)
Total Time: 0 hours 4 minutes 55.0 seconds (295 seconds)
BORLAND (optimized for 386 and for size)
Peak memory used: 1152871 bytes
Time For Parse: 0 hours 0 minutes 1.0 seconds (1 seconds)
Time For Trace: 0 hours 5 minutes 51.0 seconds (351 seconds)
Total Time: 0 hours 5 minutes 52.0 seconds (352 seconds)
BORLAND (optimized for Pentium Pro and for speed)
Peak memory used: 1152871 bytes
Time For Parse: 0 hours 0 minutes 1.0 seconds (1 seconds)
Time For Trace: 0 hours 5 minutes 51.0 seconds (351 seconds)
Total Time: 0 hours 5 minutes 52.0 seconds (352 seconds)
there is no higher optimization level than for pentium pro in help file
as you see results for different optimizatimizing options are the same and they
are ~20% worse than official version
> I already thought, that I'll collect money and buy MS VC++ for
> development (standard edition does not have optimizer, so I considered
> Professional Edition), but its quite expensive; if Borland's free
> version can do optimizing, then I'll go with it.
I stay with it. I like museums :-)
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wlodzimierz ABX Skiba wrote in message <3addbd03@news.povray.org>...
> here are results:
Ough, I made mistake !
I missed that there are two places in makefile where options are gathered. And
therefore all the time compilation was the same - for pentium and for speed. Now
corrected results:
OFFICIAL (optimized for pentium 2) 4:55
BORLAND (optimized for 386 and for size) 5:42
BORLAND (optimized for Pentium Pro and for speed) 5:13
still not as good as VC++ but if I must choose I want pay for better hardware
instead of compiler becouse it gives me benefits with other software too.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wlodzimierz ABX Skiba wrote:
>
> Wlodzimierz ABX Skiba wrote in message <3addbd03@news.povray.org>...
> > here are results:
>
> Ough, I made mistake !
> I missed that there are two places in makefile where options are gathered. And
> therefore all the time compilation was the same - for pentium and for speed. Now
> corrected results:
>
> OFFICIAL (optimized for pentium 2) 4:55
> BORLAND (optimized for 386 and for size) 5:42
> BORLAND (optimized for Pentium Pro and for speed) 5:13
>
Hmm, this is quite good, ca 6% slowdown is quite acceptable for free
version. So I think that I give it a try again.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
