Mark Gordon wrote:

> On Thu, 01 Aug 2002 18:58:13 -0400, Micha Riser wrote:
> 
>> I see quite some work has been done with unix source, the configure and
>> so. It would be nice to pass optimization flags to configure. Any
>> possibility to build a version with x11 support only (which would be a
>> bit smaller)?
> 
> A binary? I can look into that.  I plan to add a bunch more options to
> configure.
> 

I just wondered why the binary had to be 6MB big when the 3.1 was only 
around 1MB. I see now this comes mainly from the '-static' flag for the 
compiler. Without it is only around 1.5MB. Also the 6MB can be reduced to 
about 3MB when using '-static -s'. 

Am I wrong or would the binary (with '-static' compilation) get smaller 
when you remove support for vga and svga?

- Micha


-- 
http://objects.povworld.org - the POV-Ray Objects Collection

Post a reply to this message

It probably would be best to include such a povray.conf into source and put 
it into the correct place when 'make install' is done.

-- 
http://objects.povworld.org - the POV-Ray Objects Collection

Post a reply to this message

Micha Riser <mri### [at] gmxnet> wrote:
> It probably would be best to include such a povray.conf into source and put 
> it into the correct place when 'make install' is done.

  And allow everything by default? No thanks!
  Same defaults as in Windows, thanks.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

Micha Riser <mri### [at] gmxnet> wrote:
> I just wondered why the binary had to be 6MB big when the 3.1 was only 
> around 1MB. I see now this comes mainly from the '-static' flag for the 
> compiler. Without it is only around 1.5MB. Also the 6MB can be reduced to 
> about 3MB when using '-static -s'. 

  I don't even understand what is the '-static' doing there. It only causes
linkage problems (because not every library necessarily has a static version;
if you don't specify the type of linkage, the one available is used, be it
static or dynamic). And as noted, it also enormously grows the binary.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

On Sat, 03 Aug 2002 06:38:36 -0400, Warp wrote:

> Micha Riser <mri### [at] gmxnet> wrote:
>> I just wondered why the binary had to be 6MB big when the 3.1 was only
>> around 1MB. I see now this comes mainly from the '-static' flag for the
>> compiler. Without it is only around 1.5MB. Also the 6MB can be reduced
>> to about 3MB when using '-static -s'.
> 
>   I don't even understand what is the '-static' doing there. It only
>   causes
> linkage problems (because not every library necessarily has a static
> version; if you don't specify the type of linkage, the one available is
> used, be it static or dynamic). And as noted, it also enormously grows
> the binary.
 
I was making a static binary for the official release, since that's more
likely to run on a wide variety of platforms.  I need to tweak the
configure script so that dynamic linking is the default, though.  I'd
meant to do that but forgot.  It will be fixed in the next version.

-Mark Gordon

Post a reply to this message

On Sat, 03 Aug 2002 06:36:11 -0400, Warp wrote:

> Micha Riser <mri### [at] gmxnet> wrote:
>> It probably would be best to include such a povray.conf into source and
>> put it into the correct place when 'make install' is done.
> 
>   And allow everything by default? No thanks! Same defaults as in
>   Windows, thanks.
 
An alternative would be to install a system-wide default file that
contains the current defaults but has the other ones in it as well,
commented out. Then the "you can't do that" error should refer the user to
that file. I'm thinking the system-wide default file should have lots and
lots of comments.

-Mark Gordon

Post a reply to this message

In article <3d4bb21a@news.povray.org>, Warp <war### [at] tagpovrayorg> 
wrote:

> Micha Riser <mri### [at] gmxnet> wrote:
> > It probably would be best to include such a povray.conf into source and put 
> > it into the correct place when 'make install' is done.
> 
>   And allow everything by default? No thanks!
>   Same defaults as in Windows, thanks.

The file could have the same defaults there are now, it would still be 
easier to edit an existing file than to figure out how to create one. Or 
use POV itself to create the file...something like "povray --permissions 
blahblah".

-- 
Christopher James Huff <chr### [at] maccom>
POV-Ray TAG e-mail: chr### [at] tagpovrayorg
TAG web site: http://tag.povray.org/

Post a reply to this message

Mark Gordon <mtg### [at] povrayorg> wrote:
> I was making a static binary for the official release, since that's more
> likely to run on a wide variety of platforms.  I need to tweak the
> configure script so that dynamic linking is the default, though.  I'd
> meant to do that but forgot.  It will be fixed in the next version.

  Remember to check the libtiff problem when linking dynamically... I don't
recall now what was it, but I remember that I had to always specify a
static version (ie. /some/path/libtiff.a) in order for the linking to succeed.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

In article <3d49e4d4@news.povray.org> , Warp <war### [at] tagpovrayorg>  wrote:

>   I doubt that *compiling* things in Windows is any easer than in Unix.

I think compiling POV-Ray in general is not easy for non-professional
programmers.  I think the little note I wrote (based on some other/older
notes plus my own additions) for the Mac version of the source code is very
valid for the Unix and Windows platforms as well - except for the references
to specific tools of course ;-)

>>>
This is a little intro to get you started compiling POV-Ray for Mac OS.  Let
us first remind you that the POV-Team does not provide support compiling or
understanding the source code.  We do not recommend compiling the source
code on your own unless you have substancial knowledge of C and C++
programming.  You will further need experience building large multi-file,
multi-library projects with the compiler you use (most likely Metrowerks
CodeWarrior).  If you do not have this knowledge, attempts to build POV-Ray
will be a very frustrating experience.  In general there is no need to
compile POV-Ray on your own; the compiled and tested versions are available
for download at www.povray.org.

Now, if you still want to continue, this file is just a guide to get you
started.  It is by no means complete, and you may run into problems with
your individual configuration.  This is in particular the case if you are
using a newer version of the tools we used at the time we prepared the
source code archive.
<<<

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message