hi,

i managed to compile megapov 1.0 using cygwin, (i installed
libpng runtime instead of libpng develop, the rest was ok)

i used a standard cygwin install, and added:
 gcc
 binutils
 make
 m4          (i use this for f-cpu in linux)
 python      to run the pov->html script
 libpng      (first runtime, then develop)
 jpeg
 tiff

i used standard unix src + povcyg_350c_src

after "strip" i got a 1,59 Mb EXE, witch works very nicely.
(as long as cygwin1.dll is added)

Q: reading the output of "make -h", this is not what i should do:
make -mno-cygwin  no_disp
but what is the correct way to use the -mno-cygwin options ?

Q i changed:
 #define DISTRIBUTION_MESSAGE_2 VERSIONBUILDERS_MESSAGE
into:
 #define DISTRIBUTION_MESSAGE_2 "VERSIONBUILDERS_MESSAGE"
is that ok? (see next Q.)

Q it doesn't understand the "#version unofficial MegaPOV 1.0;" line
should i define this somewhere in the source ?

can anyone shed some light on this ?
jaap

Post a reply to this message

Jaap wrote:
>hi,

oh great, just did a search for my own messages...
i only used my first name as user name, but:
I am Jaap Stolk (not Jaap Frank, even if he is Dutch to...)

>jaap jws### [at] yahoocom
>

Post a reply to this message

Jaap wrote:
> 
> i managed to compile megapov 1.0 using cygwin, (i installed
> libpng runtime instead of libpng develop, the rest was ok)
> 
> [...]
> 
> Q: reading the output of "make -h", this is not what i should do:
> make -mno-cygwin  no_disp
> but what is the correct way to use the -mno-cygwin options ?
> 

Why don't you use the megapov source package for MinGW as it is supplied
on the Megapov site:

http://megapov.inetart.net/megapov-1.0_mingw_s.zip

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 31 Dec. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message