POV-Ray : Newsgroups : povray.binaries.utilities : POV-Ray 3.5 makefile for Inprise (Borland) free command-line tools Server Time
31 Oct 2024 22:20:15 EDT (-0400)
  POV-Ray 3.5 makefile for Inprise (Borland) free command-line tools (Message 1 to 10 of 18)  
Goto Latest 10 Messages Next 8 Messages >>>
From: Vahur Krouverk
Subject: POV-Ray 3.5 makefile for Inprise (Borland) free command-line tools
Date: 3 Oct 2002 18:19:45
Message: <3D9CC349.8080502@starman.ee>
As subject says :-) File contains readme file with detailed instructions.


Post a reply to this message


Attachments:
Download 'borland.zip' (5 KB)

From: Tony[B]
Subject: Re: POV-Ray 3.5 makefile for Inprise (Borland) free command-line tools
Date: 3 Oct 2002 19:34:16
Message: <3d9cd3f8$1@news.povray.org>
Wow! Talk about detailed. That's a lot of work to get POV to compile. I'm
about to try it out. Thanks in advance for all the hard work you put into
this, Vahur! I know I wouldn't have had the time or knowledge to do it all
alone.

--
Anthony Bennett


Post a reply to this message

From: Tony[B]
Subject: Re: POV-Ray 3.5 makefile for Inprise (Borland) free command-line tools
Date: 3 Oct 2002 23:31:14
Message: <3d9d0b82@news.povray.org>
Success! Thank you!! :-D

--
Anthony


Post a reply to this message

From: Vahur Krouverk
Subject: Re: POV-Ray 3.5 makefile for Inprise (Borland) free command-line tools
Date: 4 Oct 2002 15:29:35
Message: <3D9DECEA.6090907@starman.ee>
Tony[B] wrote:
> Success! Thank you!! :-D

De nada!
But if You think, that mere 'Thank you' is sufficient, then think again! 
Now You have to provide some investment return (i.e. patches, defect 
corrections etc.)!

j/k, of course:-)
But seriously talking I'd like to know, whether there were omissions or 
shortcomings in documentation or makefile in order to improve them. I 
finished this ca. 1.30 AM (4 hours past usual bed-time!!!, but I got hit 
by this can't-stop-before-finished flow!) and I'm not very sure, that 
readme is quite readable or understandable by others. So if you have (or 
someone else has) suggestions or corrections, then I'd like to hear them!


Post a reply to this message

From: Tony[B]
Subject: Re: POV-Ray 3.5 makefile for Inprise (Borland) free command-line tools
Date: 4 Oct 2002 18:16:13
Message: <3d9e132d$1@news.povray.org>
> But if You think, that mere 'Thank you' is sufficient, then think again!
> Now You have to provide some investment return (i.e. patches, defect
> corrections etc.)!

Of course! That was the whole point of compiling POV. :) It will be a long
time before you see anything from me, though. The code looks perfect to my
inexperienced eyes, so rather than trying to optimize what they've got there
right now, I'll be doing research into (dare I say) better algorithms which
produce at least equally good results. Wish me luck! :)

> But seriously talking I'd like to know, whether there were omissions or
> shortcomings in documentation or makefile in order to improve them. I
> finished this ca. 1.30 AM (4 hours past usual bed-time!!!

Only thing that I had to do was find htmlhelp.lib and winmm.lib. I used
implib (as per a suggestion on some site I've lost the URL to) to extract
winmm.lib from system32\winmm.dll. Oh, and I renamed it .obj. I have no idea
whether this is good or bad, all I know is that POV compiled and hasn't
crashed yet... It's just very slow compared to the official binary. About
half speed. :(

--
Anthony


Post a reply to this message

From: Vahur Krouverk
Subject: Re: POV-Ray 3.5 makefile for Inprise (Borland) free command-line tools
Date: 5 Oct 2002 05:44:53
Message: <3D9EB55E.700@starman.ee>
Tony[B] wrote:

> 
> Only thing that I had to do was find htmlhelp.lib and winmm.lib. I used
> implib (as per a suggestion on some site I've lost the URL to) to extract
> winmm.lib from system32\winmm.dll. Oh, and I renamed it .obj. I have no idea
> whether this is good or bad, all I know is that POV compiled and hasn't
> crashed yet... 
Which Windows version you have? In my system (W2K) there was no need for 
winmm.lib.

> It's just very slow compared to the official binary. About
> half speed. :(
> 
You get what you pay for: Inprise compiler does not produce so good 
code, as MS, Intel or gcc. Did you compiled optimized version of it? By 
default makefile has debug compiler flags (without any optimization) in 
order to make debugging easier. Although to me it seems, that these 
optimizing flags do nothing, it will produce code, which has same speed :-(


Post a reply to this message

From: ABX
Subject: Re: POV-Ray 3.5 makefile for Inprise (Borland) free command-linetools
Date: 6 Oct 2002 14:37:17
Message: <dj01qugogjpd37fu88ojedap5ab3ns316o@4ax.com>
On Fri, 04 Oct 2002 22:32:58 +0300, Vahur Krouverk <vkr### [at] starmanee>
> I'm not very sure, that 
> readme is quite readable or understandable by others.

I will check it. Thank for your effort.

ABX


Post a reply to this message

From: ABX
Subject: Re: POV-Ray 3.5 makefile for Inprise (Borland) free command-line tools
Date: 21 Oct 2002 04:43:39
Message: <pce7rugbsntvn8aboobq3ea069erg1q7k3@4ax.com>
On Fri, 4 Oct 2002 18:16:01 -0400, "Tony[B]" <ben### [at] catholicorg> wrote:
> Only thing that I had to do was find htmlhelp.lib and winmm.lib. I used
> implib (as per a suggestion on some site I've lost the URL to) to extract
> winmm.lib from system32\winmm.dll. Oh, and I renamed it .obj. I have no idea
> whether this is good or bad, all I know is that POV compiled and hasn't
> crashed yet...

That's wrong IMO. I have thought about that problem and found the reason.
First of all You don't have to extract winmm.lib from dll. It is already
present in free borland but not in main LIB\ but in subfolder LIB\PSDK.

And you don't have to rename it to obj. It can be linked directly as
winmm.lib. Just make optional two pragmas from pvengine.c.

#ifndef __BORLANDC__
  #pragma comment(lib, "htmlhelp")
  #pragma comment(lib, "winmm")
#endif

> It's just very slow compared to the official binary. About
> half speed. :(

Exactly. Standard benchmark started on Win95 with PII 233 128 MB
POVWin  - 13h 51m 14s
PoPOVWin - 7h 00m 24s

ABX


Post a reply to this message

From: Vahur Krouverk
Subject: Re: POV-Ray 3.5 makefile for Inprise (Borland) free command-line tools
Date: 27 Oct 2002 03:33:42
Message: <3DBBA4F0.1090602@starman.ee>
ABX wrote:
> On Fri, 4 Oct 2002 18:16:01 -0400, "Tony[B]" <ben### [at] catholicorg> wrote:
> 
>>Only thing that I had to do was find htmlhelp.lib and winmm.lib. I used
>>implib (as per a suggestion on some site I've lost the URL to) to extract
>>winmm.lib from system32\winmm.dll. Oh, and I renamed it .obj. I have no idea
>>whether this is good or bad, all I know is that POV compiled and hasn't
>>crashed yet...
> 
> 
> That's wrong IMO. I have thought about that problem and found the reason.
> First of all You don't have to extract winmm.lib from dll. It is already
> present in free borland but not in main LIB\ but in subfolder LIB\PSDK.
> 
> And you don't have to rename it to obj. It can be linked directly as
> winmm.lib. Just make optional two pragmas from pvengine.c.
> 
> #ifndef __BORLANDC__
>   #pragma comment(lib, "htmlhelp")
>   #pragma comment(lib, "winmm")
> #endif
> 

I looked at my code and I stand corrected in my previous statement (_In 
my system (W2K) there was no need for winmm.lib._): as it appears, i've 
commented out both pragma directive lines in pvengine.c and therefore it 
linked OK in my case. So best solution for given problem would be indeed 
to make these pragmas conditional as above.


Post a reply to this message

From: ABX
Subject: Re: POV-Ray 3.5 makefile for Inprise (Borland) free command-linetools
Date: 28 Oct 2002 03:02:30
Message: <0crpruo8cm0t4t2dkim4ra8tc1k2rgpufh@4ax.com>
On Sun, 27 Oct 2002 10:33:52 +0200, Vahur Krouverk <vkr### [at] starmanee>
wrote:
> I looked at my code and I stand corrected in my previous statement (_In 
> my system (W2K) there was no need for winmm.lib._): as it appears, i've 
> commented out both pragma directive lines in pvengine.c and therefore it 
> linked OK in my case. So best solution for given problem would be indeed 
> to make these pragmas conditional as above.

Vahur, since you are only brave to play with free borland compilation process,
would you like to try prepare compilation of povcmax2.dll and cmedit.dll using
notes written in $(POV35winsrc)\windows\readme.txt ? Is it mission imposible
with free borland ?

ABX


Post a reply to this message

Goto Latest 10 Messages Next 8 Messages >>>

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.