The normal order to extract (to: drive:\mingw) the files is:
(And order is apparently relevant)

mingw-runtime-3.13.tar.gz (3.12 working here)
w32api-3.7.tar.gz
binutils-2.17.50-20060824-1.tar.gz
gcc-core-3.4.5-20060117-1.tar.gz
gcc-g++-3.4.5-20060117-1.tar.gz
mingw32-make-3.81-2.tar.gz

version 3.7:
http://downloads.sourceforge.net/mingw/w32api-3.7.tar.gz?use_mirror=superb-east


makefile.gcc needs slash correction

http://stuff.povaddict.com.ar/Makefile.gcc


pov.bat for example

f:\povwin36>pov.bat

path C:\WINDOWS;C:\WINDOWS\COMMAND
path %PATH%;f:\mingw\bin;f:\mingw\ming32\bin

mingw32-make -f windows\makefiles\makefile.gcc USE_GUI=0 BUILD=debug clean
mingw32-make -f windows\makefiles\makefile.gcc USE_GUI=0 BUILD=debug


There are errors in povmsend.cpp need fixing

void Send_InitInfo()
int Send_RenderDone(bool)

w32api-3.8 errors out building povray (for Tim, my benefactor) because of the
boolean issue in JPEG Library. (assuming it might do the same here)
(never tried 3.9, once everything was finally installed correctly)

never understood how Nic used make.exe, gave up and started over.

I quit screwing with knowing the comiler version number for config.h
#define COMPILER_MAJOR_VER __MINGW32_MINOR_VERSION
#define COMPILER_MINOR_VER __MINGW32_MINOR_VERSION


povray.exe = 6,512,775 (with debug code)




>>When compiling using MinGW GCC it is reccommended to have the Compiler
>>and the source code on the same drive letter.
> Really? I have never heard that. What difference can the location of the
> source possibly make?

when a source includes a system header sometimes it can not find the header.
Its related to the fact that MinGW looks in \MinGW\Include by default.



htmlhlp.h is missing, for gui:
..lib comes in mingw

htmlhelp.h (added to mingw\include)
http://owlnext.sourceforge.net/old/download.html
see add_fil.zip



GUI:
windows/pvengine.cpp:7985: error: `HH_PRETRANSLATEMESSAGE' was not declared
in this scope
windows/pvengine.cpp:8007: error: `HH_UNINITIALIZE' was not declared in
this scope
MINGW3~4.EXE: *** [gcc_gui_debug/pvengine_pvengine.o] Error 1

precisely tons of warnings, 2 errors

this is far as I got with 4 days work

Post a reply to this message

"alphaQuad" <alp### [at] earthlinknet> wrote:
> #define COMPILER_MAJOR_VER __MINGW32_MINOR_VERSION
> #define COMPILER_MINOR_VER __MINGW32_MINOR_VERSION
>

of course that was
#define COMPILER_MAJOR_VER __MINGW32_MAJOR_VERSION
#define COMPILER_MINOR_VER __MINGW32_MINOR_VERSION

Post a reply to this message

USE_GUI=1

Got thru all the htmlhelp and HH_ errors, now
Having compiler link to dll errors


Anyone know why its not linking or know what manual explains this for mingw32
g++ core
Appears the quick start was written only for vc.net
"SO YOU WANT TO COMPILE IT NOW ??? - QUICK START FOR THE IMPATIENT"

REadme

------------------------------------------------------------------------------
The following section only matters if you want to work with the editor DLL's.
------------------------------------------------------------------------------

You may want to turn on the DEVELOPMENT macro near the top of pvengine.cpp to
modify the search path for DLL's (it's the way we test without having to copy
the DLL's to the POVWIN install dir). You probably won't want to do this if you
don't intend to build the editor DLL's.

dont need to build dlls, just want to link to them.
Copied them anyway to POVWIN install dir and to gcc_gui_debug

no help.


drowning in a sea of non-answers from google


F:/povwin36/windows/pvengine.cpp:2218: undefined reference to `PlaySoundA@12'
gcc_gui_debug/pvengine_pvtext.o: In function `Z14create_toolbarP6HWND__':
F:/povwin36/windows/pvtext.cpp:1581: undefined reference to
`_imp__ImageList_Create@20'


PlaySoundA is found in cmedit32.dll
so it seems to me the compiler has not been informed of the externals.

where would this be corrected? makefile? or another place? (and how exactly)


BUT this one boggles:
the reference is ImageList_Create (cmedit.dll)
NOT
_imp__ImageList_Create

_imp__ImageList_Create <not found
Whats up with that!

greatly appreciated,
OldPerson

Post a reply to this message

I NEVER tried to build the GUI with MinGW. Because I never needed it.

PlaySoundA and ImageList_Create are probably being called *from* 
cmedit.dll, they are part of the Windows API.

Post a reply to this message

Nicolas Alvarez <nic### [at] gmailisthebestcom> wrote:
> I NEVER tried to build the GUI with MinGW. Because I never needed it.
>
> PlaySoundA and ImageList_Create are probably being called *from*
> cmedit.dll, they are part of the Windows API.

something to do with LDFLAGS=

using the environment var LDFLAGS:
ld returns error not found for being incorrectly set;
atleast we know ld is listening.

 ... something about .a files?

what is a .a file?

more later when/if I figure this out.

wouldnt it be great if one wanted to compile this and found complete info.
my motivation is not finding such info it myself.

http://www.mingw.org/docs.shtml
its gotta be here somewhere

Post a reply to this message

alphaQuad wrote:
> wouldnt it be great if one wanted to compile this and found complete info.
> my motivation is not finding such info it myself.

Well, you could just use an operating system still supported by its maker,
together with a compiler supported by the POV-Team to compile the Windows
version of POV-Ray ;-)

	Thorsten

Post a reply to this message

Maybe a thorough comprehension of
http://edll.sourceforge.net/

with apps I could compile on VC6
just type in the name.dll in settings

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
> alphaQuad wrote:
> > wouldnt it be great if one wanted to compile this and found complete info.
> > my motivation is not finding such info it myself.
>
> Well, you could just use an operating system still supported by its maker,
> together with a compiler supported by the POV-Team to compile the Windows
> version of POV-Ray ;-)
>
>  Thorsten

Your posts continue to make me smile.

I keep thinkin' Thirstin Howl III.

Are you buyin'?

Post a reply to this message

alphaQuad wrote:
> Thorsten Froehlich <tho### [at] trfde> wrote:
>> alphaQuad wrote:
>>> wouldnt it be great if one wanted to compile this and found complete info.
>>> my motivation is not finding such info it myself.
>> Well, you could just use an operating system still supported by its maker,
>> together with a compiler supported by the POV-Team to compile the Windows
>> version of POV-Ray ;-)
>>
>>  Thorsten
> 
> Your posts continue to make me smile.
> 
> I keep thinkin' Thirstin Howl III.
> 
> Are you buyin'?

Not sure about this reference, seems to be hinting at Gilligan's Island -
anyway:

I guess you are trying to imply you either don't want to or can't spend the
money on a newer computer. Yet, you seem to have lots of time to spend on
this project (even though you say you don't want to), and at least some
basic knowledge to move along. -- I would suggest you could be a lot happier
using a current Linux distribution than an outdated Windows version...

	Thorsten

Post a reply to this message

here are the final instructions not found in pov source:


impdef comctl32 comctl32
rem dlltool --def comctl32.def --dllname comctl32.dll --output-lib libcomctl32.a

trying get sound workin with winmm:
mingw32-make -f windows\makefiles\makefile.gcc USE_GUI=1 BUILD=debug
LDFLAGS='-lcomctl32 -lwinmm'

but

G__~1.EXE: gcc_gui_debug/pvF:\povwin36: No such file or directory

pvF
pv Frontend??????

incomprehensible
prolly have better luck with fmod


The GUI is running!

to thorston: in your face! lol
you have no sense of humor and a bad attitude,
I'd be alot happier if you had a sense of humor and stayed on topic.

Gilligan

Post a reply to this message