POV-Ray : Newsgroups : povray.programming : Compiling POVRAY 3.5 using VC6.0 in Release Mode Server Time
8 Jul 2024 18:17:21 EDT (-0400)
  Compiling POVRAY 3.5 using VC6.0 in Release Mode (Message 21 to 30 of 40)  
<<< Previous 10 Messages Goto Latest 10 Messages Next 10 Messages >>>
From: Nicolas Alvarez
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 27 Nov 2007 12:13:27
Message: <474c5037$1@news.povray.org>

> or is it
> f:\povwin36> f:\msys\bin\make.exe -f f:\povwin36\windows\makefiles\makefile.gcc
> USE_GUI=0 BUILD=debug

Try it :)

I run it from the MSYS shell; which is bash, and has the PATH set to the 
right places and all. Being bash it lets you run 'configure' scripts too.


Post a reply to this message

From: alphaQuad
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 27 Nov 2007 12:25:00
Message: <web.474c5213791be382448584b70@news.povray.org>
OR

f:\msys\bin> make.exe -f f:\povwin36\windows\makefiles\makefile.gcc
USE_GUI=0 BUILD=debug

I really dont want to melt my mem or CPU here


Post a reply to this message

From: Nicolas Alvarez
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 27 Nov 2007 12:29:34
Message: <474c53fe$1@news.povray.org>


>> or is it
>> f:\povwin36> f:\msys\bin\make.exe -f 
>> f:\povwin36\windows\makefiles\makefile.gcc
>> USE_GUI=0 BUILD=debug
> 
> Try it :)

Ok, not so easy.

I tried another program with a makefile, and it indeed works from the 
normal Windows command prompt, without needing MSYS.

path %PATH%;C:\msys\bin;C:\msys\mingw\bin
make

Success.

Then I tried POV-Ray. It complained about config.h missing. Ah yeah, 
edit makefile.gcc, replace all backslashes in paths with normal slashes. 
Or the lazy way, get mine:
http://stuff.povaddict.com.ar/config.h

Tried again, got "Adjust config.h to your compiler!". Edit config.h like 
this:

On lines 55 and 56, replace 1 with 10.
On lines 67, 68, 73, and 74, replace with the correct gcc version. Do 
gcc --version to see what it is (3.4.5 on mine).

Remember to edit optout.h's DISTRIBUTION_MESSAGE2. It will give an error 
if you don't (required by license).


Post a reply to this message

From: Nicolas Alvarez
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 27 Nov 2007 12:30:36
Message: <474c543c$1@news.povray.org>

> http://stuff.povaddict.com.ar/config.h

GAH. I meant http://stuff.povaddict.com.ar/Makefile.gcc


Post a reply to this message

From: alphaQuad
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 27 Nov 2007 12:40:00
Message: <web.474c55b0791be382448584b70@news.povray.org>
Nicolas Alvarez <nic### [at] gmailisthebestcom> wrote:

> Then I tried POV-Ray. It complained about config.h missing. Ah yeah,
> edit makefile.gcc, replace all backslashes in paths with normal slashes.
> Or the lazy way, get mine:
> http://stuff.povaddict.com.ar/config.h

Not Found

The requested URL /config.h was not found on this server.
Apache/2.0.61 (Win32) PHP/5.2.5 Server at stuff.povaddict.com.ar Port 80


Post a reply to this message

From: alphaQuad
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 27 Nov 2007 13:10:00
Message: <web.474c5c65791be382448584b70@news.povray.org>
that was nearly 10 minutes big delay somewhere, anyway,

there are 2 config.h

povwin36\windows\config.h
line 55: empty
line 72:

#if __MINGW32_MINOR_VERSION == 1
#define COMPILER_MINOR_VER              "1"
#else
#error "Adjust config.h to your compiler!"
#endif




povwin36\windows\console\config.h line 55 and 56
#if __MINGW32_MINOR_VERSION == 1
#define COMPILER_MINOR_VER                             "1"


so that one (obviously), but is this a potential conflict,

or do I edit both?







F:\>path %PATH%;f:\msys\bin;f:\msys\mingw\bin
F:\>path
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;F:\MSYS\BIN;F:\MSYS\MINGW\BIN
F:\>gcc --version
GCC.EXE (GCC) 3.4.5 (mingw special)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
F:\>


Post a reply to this message

From: alphaQuad
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 27 Nov 2007 13:50:00
Message: <web.474c6563791be382448584b70@news.povray.org>
OIC (i think)


// Note that this section is supposed to be compiled with MinGW 3.2 with GCC
3.2.3

NOW is: 3.12 and 3.4.5 (i think 3.12 for runtime mingw??)
in both config.h files
but the line for minor version was "1" (thinking it should been 2)

MSYS-1.0.11-2004.04.30-1.exe
MSYS-1.0.11-20060807.tar.bz2
bash-3.1-MSYS-1.0.11-snapshot.tar.bz2

mingw-runtime-3.12.tar.gz
gcc-core-3.4.5-20060117-1.tar.gz
gcc-g++-3.4.5-20060117-1.tar.gz
w32api-3.9.tar.gz

should be "12" ?????????????????


#if __MINGW32_MAJOR_VERSION == 3
#define COMPILER_MAJOR_VER                             "3"
#else
#error "Adjust config.h to your compiler!"
#endif

#if __MINGW32_MINOR_VERSION == 12
#define COMPILER_MINOR_VER                             "12"
#else
#error "Adjust config.h to your compiler!"
#endif

#if  __GNUC__ == 3
#define GCC_MAJOR_VER                                  "3"
#else
#error "Adjust config.h to your compiler!"
#endif

#if __GNUC_MINOR__ == 4
#define GCC_MINOR_VER                                  "4"
#else
#error "Adjust config.h to your compiler!"
#endif

#if __GNUC_PATCHLEVEL__ == 5
#define GCC_PATCH_VER                                  "5"


Post a reply to this message

From: Nicolas Alvarez
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 27 Nov 2007 14:39:28
Message: <474c7270$1@news.povray.org>

> OIC (i think)
> 
> 
> // Note that this section is supposed to be compiled with MinGW 3.2 with GCC
> 3.2.3
> 
> NOW is: 3.12 and 3.4.5 (i think 3.12 for runtime mingw??)
> 
> should be "12" ?????????????????

Just edit windows/console/config.h. The windows/config.h is for the GUI 
version.

Mine worked setting it to MinGW 3.10. Try compiling, if it still gives 
the "Adjust config.h to your compiler!", try something else. I figured 
out the '10' number for mine using trial-and-error after all...


Post a reply to this message

From: alphaQuad
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 27 Nov 2007 14:45:00
Message: <web.474c735d791be382448584b70@news.povray.org>
F:\povwin36>make.exe -f windows\makefiles\makefile.gcc USE_GUI=0 BUILD=debug


g++ -c -o gcc_con_debug/povray_fileinputoutput.o -Iwindows/console -Isource -Iso
urce/patches -Isource/base -Isource/frontend -Ilibraries/jpeg -Ilibraries/png -I
libraries/zlib -Ilibraries/tiff/libtiff -Wno-multichar -Wno-conversion -DCOMMONC
TRL_VERSION=0x0400 -g   source/base/fileinputoutput.cpp
 - Cannot openMAKE: *** [gcc_con_debug/povray_fileinputoutput.o] Error 1


lost ...........

assuming it would write the file:
made dirs all over the place for it to write to
gcc_con_debug

povray_fileinputoutput.o
no such file in source

source/base/fileinputoutput.cpp
source/base/fileinputoutput.h
== true


Post a reply to this message

From: Nicolas Alvarez
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 27 Nov 2007 14:48:34
Message: <474c7492$1@news.povray.org>

> F:\povwin36>make.exe -f windows\makefiles\makefile.gcc USE_GUI=0 BUILD=debug
> 
> 
> g++ -c -o gcc_con_debug/povray_fileinputoutput.o -Iwindows/console -Isource -Iso
> urce/patches -Isource/base -Isource/frontend -Ilibraries/jpeg -Ilibraries/png -I
> libraries/zlib -Ilibraries/tiff/libtiff -Wno-multichar -Wno-conversion -DCOMMONC
> TRL_VERSION=0x0400 -g   source/base/fileinputoutput.cpp
>  - Cannot openMAKE: *** [gcc_con_debug/povray_fileinputoutput.o] Error 1
> 

Oh erm... Create the gcc_con_debug directory. For some strange reason, 
the makefile fails to create it by itself.


Post a reply to this message

<<< Previous 10 Messages Goto Latest 10 Messages Next 10 Messages >>>

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