POV-Ray : Newsgroups : povray.programming : Atempting MPW Compile ? Server Time
10 Oct 2026 11:24:36 EDT (-0400)
  Atempting MPW Compile ? (Message 1 to 26 of 26)  
From: Moon47
Subject: Atempting MPW Compile ?
Date: 5 May 2000 23:20:40
Message: <391240BA.BBBBCD38@earthlink.net>
Attempting MPW Compile ?
With little luck...
Any help would be graciously appreciated... =)
Major prob., is w/ sysMacPict.c. Listing the errors below...
I have read and tried the post in Macintosh.Users.Group "Compile 3.1g r2
under MPW MrC" by Y.Tanabe with varying success. i.e. some changes were
not sensible?

(1)These are the errors received w/ the sysMacPict from Y.Tanabe:
(2)The second set are errors from the original sysMacPict:

(1)...-->
# 5/4/00 8:43:39 PM ----- Building :mpwobj:sysMacPict.c.o
MrC C Compiler 4.1.0f1c1
Copyright (C) 1994-1999 by Apple Computer, Inc.

header size in bytes
       ^
File ":MacSource:sysMacPict.c"; line 153 #Error: missing ',' between
declaration of 'header' and 'size'
#-----------------------
} PictFHeader, *PictFHeaderPtr;
^
File ":MacSource:sysMacPict.c"; line 159 #Error: ';' or ',' expected
#-----------------------
file handle") ;
           ^
File ":MacSource:sysMacPict.c"; line 269 #Lexical error: unterminated
string
#-----------------------
                Error("PICT is to big, maximal width of PICTs to read is

                                                                       ^

File ":MacSource:sysMacPict.c"; line 391 #Lexical error: unterminated
string
#-----------------------
This way
     ^
File ":MacSource:sysMacPict.c"; line 426 #Error: missing ',' between
declaration of 'This' and 'way'
#-----------------------
Fatal error: too many errors
### MPW Shell copy - Execution of Pov-Ray.makeout terminated.
### MPW Shell copy - Execution of BuildProgram terminated.

(2)...-->
# 5/2/00 10:01:29 PM ----- Building :mpwobj:sysMacPict.c.o
MrC C Compiler 4.1.0f1c1
Copyright (C) 1994-1999 by Apple Computer, Inc.

class MacFile
      ^
File ":MacSource:sysMacPict.c"; line 111 #Error: missing ',' between
declaration of 'class' and 'MacFile'
#-----------------------
                virtual ~MacFile() { };
                        ^
File ":MacSource:sysMacPict.c"; line 115 #Error: ';' or ',' expected
#-----------------------
                virtual void WriteLine(COLOUR *line_data, int
line_number) = 0;
                        ^
File ":MacSource:sysMacPict.c"; line 117 #Error: ';' or ',' expected
#-----------------------
                virtual int ReadLine(COLOUR *line_data, int
*line_number) = 0;
                        ^
File ":MacSource:sysMacPict.c"; line 118 #Error: ';' or ',' expected
#-----------------------
};
^
File ":MacSource:sysMacPict.c"; line 119 #Error: ';' or ',' expected
#-----------------------
Fatal error: too many errors
### MPW Shell copy - Execution of Pov-Ray.makeout terminated.
### MPW Shell copy - Execution of BuildProgram terminated.


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Atempting MPW Compile ?
Date: 6 May 2000 12:03:12
Message: <39144240@news.povray.org>
In article <391240BA.BBBBCD38@earthlink.net> , Moon47 <rdm### [at] earthlinknet>
wrote:
> Attempting MPW Compile ?
> With little luck...

It is currently not possible to compile POV-Ray 3.1g with MrC without a good
portion of knowledge about mixed C/C++ compiles using MrC.  When releasing
the source code for 3.1g I simply forgot to update the makefile, and it
would have taken some time to fix it so you can compile again anyway.

> (1)These are the errors received w/ the sysMacPict from Y.Tanabe:
> (2)The second set are errors from the original sysMacPict:

For reasons of stability I suggest to use CodeWarrior, especially if you
have no or little experience with MPW and the MrC compiler or with C/C++ in
general.


       Thorsten


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Moon47
Subject: Re: Atempting MPW Compile ?
Date: 6 May 2000 13:33:15
Message: <3913088E.C534BA89@earthlink.net>
So the problems with sysMacPict exist in the makefile and not the .c &
.h files for sysMacPict...? It would help if i knew where to hunt down
the problem... Once again i have fixed current problems up until
sysMacPict. It has given me the most trouble...?

> It is currently not possible to compile POV-Ray 3.1g with MrC without
a good
> portion of knowledge about mixed C/C++ compiles using MrC.  When
releasing
> the source code for 3.1g I simply forgot to update the makefile, and
it
> would have taken some time to fix it so you can compile again anyway.

I was not happy with the CodeWarrior evaluation copy i received.
Therefore i have given up on that idea until 1. I have a new computer
that will handle the evaluation disks i currently have... ( long story )
... in short the evaluation disks will not work on my computer
specifically and they don't know why... =(
2. I have $ to buy a copy of CodeWarrior.

Yes my knowledge is minimal with C and none with C++. I have been
teaching myself C with MPW at home and plan to take C++ in the fall...

> For reasons of stability I suggest to use CodeWarrior, especially if
you
> have no or little experience with MPW and the MrC compiler or with
C/C++ in
> general.


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Atempting MPW Compile ?
Date: 6 May 2000 15:50:29
Message: <39147785@news.povray.org>
In article <3913088E.C534BA89@earthlink.net> , Moon47 <rdm### [at] earthlinknet>
wrote:

> So the problems with sysMacPict exist in the makefile and not the .c &
> .h files for sysMacPict...? It would help if i knew where to hunt down
> the problem... Once again i have fixed current problems up until
> sysMacPict. It has given me the most trouble...?

No, the problem is rather strange:  The early versions of POV-Ray 3.1,
including at least 3.1 and 3.1a used a different sysMacPict code.
I then rewrote it and placed it into a two classes and wrote an adaptation
layer (from C++ to the C function POV-Ray expects) to more easily switch
between Pict and Movie output.  As CodeWarrior allows to mix C and C++
source files without requiring to switch compilers there are no problems
there.  With the MPW MrC compiler things are different and you actually need
MrC to compile most of the source and MrCpp to compile sysMacPict.cp .
there is only one catch: The linker does not like the slightly different
object formats, at least the last time I tried.

The real solution to the problem would involve the following steps in
splitting up the MPW makefile:

- move the PNG sources into a static library -> new makefile using MrC
- move the ZLIB sources into a static librar y -> new makefile using MrC
- remove the PNG and ZLIb sources from the current POV-Ray makefile
- add the PNG and ZLIB static libraries to the current POV-Ray makefile
- change the POV-Ray makefile to use MrCpp
- build PNG and ZLIb libraries, then build POV-Ray

I will do this for the POV-Ray Mac 3.5 source files, but my time does not
permit me to do this for 3.1 right now :-(


       Thorsten


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Moon47
Subject: Re: Atempting MPW Compile ?
Date: 6 May 2000 16:54:39
Message: <391337C1.805E9D4E@earthlink.net>
Thank you this does help... Not allot, but that is fault of my low
knowledge and understanding. But hopefully as this grows this will give
me a direction to start in to solve the problem. thank you again for
your input...

> I will do this for the POV-Ray Mac 3.5 source files, but my time does
not
> permit me to do this for 3.1 right now :-(

Understandable...
Cant Wait to see what is in store...


Post a reply to this message

From: Moon47
Subject: Re: Atempting MPW Compile ?
Date: 7 May 2000 14:57:10
Message: <39146DBC.A614DB9C@earthlink.net>
I am trying to compile w/ out the pesky sysMacPict till i have time to
read up and fix the make file as suggested...
I ran into another problem:

 if(GetControlData(controlList, 0, kControlListBoxListHandleTag,
sizeof(ListHandle), (Ptr)(&list), &actualSize) != noErr)
                                   ^
File ":MacSource:TextEditorUtils.c"; line 501 #Error: undefined
identifier 'kControlListBoxListHandleTag'

Why is this where should this have been defined...?


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Atempting MPW Compile ?
Date: 7 May 2000 17:07:41
Message: <3915db1d$1@news.povray.org>
In article <39146DBC.A614DB9C@earthlink.net> , Moon47 <rdm### [at] earthlinknet>
wrote:

> I am trying to compile w/ out the pesky sysMacPict till i have time to
> read up and fix the make file as suggested...
> I ran into another problem:
>
>  if(GetControlData(controlList, 0, kControlListBoxListHandleTag,
> sizeof(ListHandle), (Ptr)(&list), &actualSize) != noErr)
>                                    ^
> File ":MacSource:TextEditorUtils.c"; line 501 #Error: undefined
> identifier 'kControlListBoxListHandleTag'
>
> Why is this where should this have been defined...?
>

Two possible reasons: Either your Universal Interfaces are too old, I think
3.2 is required. Or, ControlDefinitions.h is not included properly.


     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

From: Moon47
Subject: Re: Atempting MPW Compile ?
Date: 8 May 2000 20:09:38
Message: <39160878.F3C312FD@earthlink.net>
Thank you,

I believe that anything having to do w/ C/C++ is most current including
interfaces. Although i am not sure what "Universal Interfaces" are i
have nothing ( as far as i know ) titled "universal..." in MPW...

ControlDefinitions.h was not included at all as far as i could see i
included it after TextEditorUtils.h at the top... it ran fine...

More problems w/: LIGHTING.c

I appreciate all the help. I hope this does not take out too much of
your time.
Btw would this dissuasion be better fit in the Bug Report forum ? If so
maybe i should start a new thread in Bug Report...?

Thanks again this will help immensely in the long run...
And keep in mind i am in no hurry, reply at your own convenience... I
still have other studding to do besides working on the bugs... Thanks...
Ryan Mooney.

# 5/7/00 5:57:54 PM ----- Building :mpwobj:LIGHTING.c.o
MrC C Compiler 5.0.0d1c1
Copyright (C) 1994-2000 by Apple Computer, Inc.

        Warp_EPoint(TPoint, IPoint, (TPATTERN *)Texture);
                                                       ^
File ":SOURCE:LIGHTING.c"; line 2230 #Error: 4 actual arguments expected
for Warp_EPoint
#-----------------------
        Warp_EPoint (TPoint, IPoint, (TPATTERN *)Texture);
                                                        ^
File ":SOURCE:LIGHTING.c"; line 2238 #Error: 4 actual arguments expected
for Warp_EPoint
#-----------------------
    Warp_EPoint (TPoint, IPoint, (TPATTERN *)Texture);
                                                    ^
File ":SOURCE:LIGHTING.c"; line 2270 #Error: 4 actual arguments expected
for Warp_EPoint
#-----------------------
            (void)Compute_Ambient(Intersection->IPoint, Raw_Normal,
AmbCol, Weight * Max_Radiosity_Contribution);

^
File ":SOURCE:LIGHTING.c"; line 2497 #Error (Arg #3): cannot implicitly
convert
from: (float *)
to  : (double *)
#-----------------------
}
^
File ":SOURCE:LIGHTING.c"; line 2702 #
### Warning 29: Local variable 'Normal_Direction' is not used within
function 'compute_lighted_texture'
#-----------------------
### MPW Shell copy - Execution of Pov-Ray.makeout terminated.
### MPW Shell copy - Execution of BuildProgram terminated.


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Atempting MPW Compile ?
Date: 8 May 2000 22:47:14
Message: <39177c32$1@news.povray.org>
In article <39160878.F3C312FD@earthlink.net> , Moon47 <rdm### [at] earthlinknet>
wrote:

> I believe that anything having to do w/ C/C++ is most current including
> interfaces. Although i am not sure what "Universal Interfaces" are i
> have nothing ( as far as i know ) titled "universal..." in MPW...

It is the "Interfaces&Libraries" folder, you can always get the most recent
version of Universal Interfaces (basically header files and stub libraries)
from <http://developer.apple.com/sdk/index.html>.

> ControlDefinitions.h was not included at all as far as i could see i
> included it after TextEditorUtils.h at the top... it ran fine...
>
> More problems w/: LIGHTING.c
>
> I appreciate all the help. I hope this does not take out too much of
> your time.

No problem, I should have checked the MPW makefile before releasing the
source code.  The thing is that MPW MrC compiles have always been a mess to
set up, CodeWarrior is easier to use and allows to forget about such issues
like header files at all (also this is not always good) by using precompiled
headers (which is also faster when compiling complex projects like POV-Ray).

But I have to admit that I really do not know why the casts and function
calls in lighting.c should not compile, the only idea I can come up with is
that you have some ANSI C or strong error checking option activated.

BTW, you should not be using MrC 5.0.0d1c1, this is definitely a bad idea
(especially with MrC where they are still fixing the parser to support full
ISO C++ using a "developmental", meaning pre-alpha version is a bad idea).
You should use MrC 4.1 (the current final version of MrC) and once you get
there, you should also make sure you are running the final PPCLink in case
you are not.

> Btw would this dissuasion be better fit in the Bug Report forum ? If so
> maybe i should start a new thread in Bug Report...?

No, povray.programming is the right group.  For all practical purposes the
source code is unsupported anyway, so there is no way to report compiling
problems as bugs :-)


      Thorsten


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Moon47
Subject: Re: Atempting MPW Compile ?
Date: 10 May 2000 02:04:51
Message: <3917AD3C.3087475B@earthlink.net>
Last one i hope i almost thought i was done...
Well only 30 or so more files to go out of a couple hundred...
Any idea... Why is it trying to "convert" int to what looks like a call
to some funct? File OPTIN.c.o:

# 5/8/00 11:53:02 PM ----- Building :mpwobj:OPTIN.c.o
MrC C Compiler 4.1.0f1c1
Copyright (C) 1994-1999 by Apple Computer, Inc.

             Histogram_File_Handle = GET_SYS_FILE_HANDLE () ;
                                                            ^
File ":SOURCE:OPTIN.c"; line 1653 #Error: cannot implicitly convert
from: (int)
to  : (struct file_handle_struct *)
#-----------------------
### MPW Shell - Execution of Pov-Ray.makeout terminated.
### MPW Shell - Execution of BuildProgram terminated.


Post a reply to this message

From: Y Tanabe
Subject: Re: Atempting MPW Compile ?
Date: 10 May 2000 03:09:35
Message: <39190B32.69B72E3A@kh.rim.or.jp>
Mr. Ryan Mooney or Moon47

If you use my arranging SysMacPict.h and SysMacPict.c,so this may help I
think.
But if you use old SysmacPict.h,c, then you have to modify config.h for
GET_SYS_FILE_HANDLE().
The old SysMacPict can not work continue rendering well.
Would you please understand difference with MacSource and Source folder,
MacSource files are defined by config.h and Source files are defined by
frame.h.

Y.Tanabe
Kobe,Japan

//START

1.)
Replace and add
 sysMacPict.c
 sysMacPict.h

2.)
Add  Boolean  flag to struct file_handle_struct in "FRAME.H"

struct file_handle_struct
{
 char  *filename;
 int  mode;
 int  width, height;
 int  buffer_size;
 char  *buffer;
 FILE  *file;
 int  file_type;  /* What format the output file is */
 int   (*Open_File_p) (struct file_handle_struct *handle,char *name, int
*width, int *height, int buffer_size, int mode);
 void   (*Write_Line_p) (struct file_handle_struct *handle,COLOUR
*line_data, int line_number);
 int   (*Read_Line_p) (struct file_handle_struct *handle,COLOUR
*line_data, int *line_number);
 void   (*Read_Image_p) (IMAGE *Image, char *filename);
 void   (*Close_File_p) (struct file_handle_struct *handle);
//TFC ADD
 Boolean  flag;
};

3.)
File ":MacSource:config.h"; line 379
File ":MacSource:PovMac.h"; line 71
change
#include <MacTypes.h>
 to
#include <Types.h>

File ":MacSource:PovMac.h"; line 88
change
#include <ControlDefinitions.h>
to
//#include <ControlDefinitions.h>

File ":MacSource:DialogUtils.c"; line 901
change
#ifdef __UseNavEventData
 switch(callBackParms->eventData.eventDataParms.event->what)
#else
  switch(callBackParms->eventData.event->what)
#endif
to
//#ifdef __UseNavEventData
// switch(callBackParms->eventData.eventDataParms.event->what)
//#else
  switch(callBackParms->eventData.event->what)
//#endif


File ":MacSource:DialogUtils.c"; line 911
change
#ifdef __UseNavEventData
    pWindow =
(WindowPtr)(callBackParms->eventData.eventDataParms.event->message);
#else
    pWindow = (WindowPtr)(callBackParms->eventData.event->message);
#endif
to
//#ifdef __UseNavEventData
//    pWindow =
(WindowPtr)(callBackParms->eventData.eventDataParms.event->message);
//#else
    pWindow = (WindowPtr)(callBackParms->eventData.event->message);
//#endif

File ":SOURCE:OPTIN.c"; line 1653
add top
#include "sysMacPict.h"
change
 Histogram_File_Handle = GET_SYS_FILE_HANDLE ();
to
 Histogram_File_Handle = Get_MacPICT_File_Handle();

File ":SOURCE:POVRAY.c"; line 1043
add top
#include "sysMacPict.h"
change
 case 'S' : Output_File_Handle = GET_SYS_FILE_HANDLE();
def_ext=SYS_DEF_EXT; break;
to
case 'S' : Output_File_Handle = Get_MacPICT_File_Handle();
def_ext=SYS_DEF_EXT; break;

File ":SOURCE:PARSTXTR.c"; line 162
add top
#include "sysMacPict.h"
change
READ_SYS_IMAGE(Image, Name);
to
Read_MacPICT_Image(Image, Name);

File ":MacSource:DialogUtils.h"; line 116
change
// We don't need prototypes here, they are in Controls.h!
/*
pascal OSErr GetBevelButtonMenuValue(ControlHandle inButton, SInt16
*outValue);
pascal OSErr SetBevelButtonMenuValue(ControlHandle inButton, SInt16
inValue);
pascal OSErr GetBevelButtonMenuHandle(ControlHandle inButton, MenuHandle
*outHandle);
pascal OSErr SetBevelButtonGraphicAlignment(ControlHandle inButton,
ControlButtonGraphicAlignment inAlign, SInt16 inHOffset, SInt16
inVOffset);
pascal OSErr GetImageWellContentInfo(ControlHandle inButton,
ControlButtonContentInfoPtr info);
pascal OSErr SetImageWellContentInfo(ControlHandle inButton,
ControlButtonContentInfoPtr info);
*/
to
// We don't need prototypes here, they are in Controls.h!
pascal OSErr GetBevelButtonMenuValue(ControlHandle inButton, SInt16
*outValue);
pascal OSErr SetBevelButtonMenuValue(ControlHandle inButton, SInt16
inValue);
pascal OSErr GetBevelButtonMenuHandle(ControlHandle inButton, MenuHandle
*outHandle);
pascal OSErr SetBevelButtonGraphicAlignment(ControlHandle inButton,
ControlButtonGraphicAlignment inAlign, SInt16 inHOffset, SInt16
inVOffset);
pascal OSErr GetImageWellContentInfo(ControlHandle inButton,
ControlButtonContentInfoPtr info);
pascal OSErr SetImageWellContentInfo(ControlHandle inButton,
ControlButtonContentInfoPtr info);

File ":MacSource:DialogUtils.c"; line 1048
change
#if !defined(powerc) && !defined (__powerc)
to
//#if !defined(powerc) && !defined (__powerc)

File ":MacSource:DialogUtils.c"; line 1119
change
#endif
to
//#endif

4.)
POV-Ray.make
change
{AppName} �� {CheckMakeFile} {AppName} {PovRayMacDir}PovMac.rsrc
{PovRayMacDir}mpwRsrcs.r
  # Make an XSym (debugging) file
#  {ShowMakeSymProgress}
#  MakeSym {MakeSymOptions} {AppName}.xcoff
  {ShowRezProgress}
  {RezTool} {PovRayMacDir}mpwRsrcs.r -o {Targ} -append
  # Call Thorsten's tool to fix up the application's stack size
  set StackSize 600000
  Echo "# `date -s` ----- Setting App stack size to {StackSize}"
  ChangeAppStack {AppName} -appstack StackSize
  # Set file's creator type, turn on bundle bit, turn off inited bit
  SetFile {Targ} -t APPL -c {AppSignature} -a Bi

to
{AppName} �� {CheckMakeFile} {AppName} {PovRayMacDir}PovMac.rsrc
{PovRayMacDir}mpwRsrcs.r
  # Make an XSym (debugging) file
#  {ShowMakeSymProgress}
#  MakeSym {MakeSymOptions} {AppName}.xcoff
  {ShowRezProgress}
  {RezTool} {PovRayMacDir}mpwRsrcs.r -o {Targ} -append
  # Call Thorsten's tool to fix up the application's stack size
#  set StackSize 600000
#  Echo "# `date -s` ----- Setting App stack size to {StackSize}"
#  ChangeAppStack {AppName} -appstack StackSize
  # Set file's creator type, turn on bundle bit, turn off inited bit
  SetFile {Targ} -t APPL -c {AppSignature} -a Bi

5.)
mpwRsrcs.r
add top
#include "CodeFragmentTypes.r"
#define kDefaultStackSize 307200
add bottom
resource 'cfrg' (0)
{
 {
  kPowerPC,
  kFullLib,
  kNoVersionNum,
  kNoVersionNum,
  kDefaultStackSize,
  kNoAppSubFolder,
  kIsApp,
  kOnDiskFlat,
  kZeroOffset,
  kWholeFork,
  "POV-Ray"
 }
};

//END



Moon47 wrote:

> Last one i hope i almost thought i was done...
> Well only 30 or so more files to go out of a couple hundred...
> Any idea... Why is it trying to "convert" int to what looks like a call
> to some funct? File OPTIN.c.o:
>
> # 5/8/00 11:53:02 PM ----- Building :mpwobj:OPTIN.c.o
> MrC C Compiler 4.1.0f1c1
> Copyright (C) 1994-1999 by Apple Computer, Inc.
>
>              Histogram_File_Handle = GET_SYS_FILE_HANDLE () ;
>                                                             ^
> File ":SOURCE:OPTIN.c"; line 1653 #Error: cannot implicitly convert
> from: (int)
> to  : (struct file_handle_struct *)
> #-----------------------
> ### MPW Shell - Execution of Pov-Ray.makeout terminated.
> ### MPW Shell - Execution of BuildProgram terminated.


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Atempting MPW Compile ?
Date: 10 May 2000 10:07:50
Message: <39196d36$1@news.povray.org>
In article <3917AD3C.3087475B@earthlink.net> , Moon47 <rdm### [at] earthlinknet>
wrote:

> # 5/8/00 11:53:02 PM ----- Building :mpwobj:OPTIN.c.o
> MrC C Compiler 4.1.0f1c1
> Copyright (C) 1994-1999 by Apple Computer, Inc.
>
>              Histogram_File_Handle = GET_SYS_FILE_HANDLE () ;
>                                                             ^
> File ":SOURCE:OPTIN.c"; line 1653 #Error: cannot implicitly convert
> from: (int)
> to  : (struct file_handle_struct *)

If you are compiling without sysMacPict.cp you need to fix config.h. To do
so remove there lines from config.h:

// Machine-specific image_map file routines (PICT for the Mac, sysMacPict.c)
#define GET_SYS_FILE_HANDLE() MacFile_GetFileHandle()
#define READ_SYS_IMAGE(i,n)  MacFile_ReadImage((i),(n))
#define SYS_DEF_EXT    ".pict"



       Thorsten


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Moon47
Subject: Re: Atempting MPW Compile ?
Date: 10 May 2000 18:09:19
Message: <39188F48.74DBF03@earthlink.net>
That did make sense but did not fix the problem. Neither OPTIN.c nor
OPTIN.h use the config.h header file in the includes...?

Why is it trying to "implicitly convert
> from: (int)
> to  : (struct file_handle_struct *)"

This does not make sense to me...?


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Atempting MPW Compile ?
Date: 10 May 2000 20:40:48
Message: <391a0190@news.povray.org>
In article <391### [at] earthlinknet> , Moon47 <rdm### [at] earthlinknet> 
wrote:

> That did make sense but did not fix the problem. Neither OPTIN.c nor
> OPTIN.h use the config.h header file in the includes...?

Yes, they do. config.h gets included via frame.h.

> Why is it trying to "implicitly convert
>> from: (int)
>> to  : (struct file_handle_struct *)"
>
> This does not make sense to me...?

Because it does not know the function and by default all functions return
"int" in K&R C.

Oh, and this code should work. Are you sure you removed the three defines
from the right config.h (the one in the MacSource folder)? You may also want
to try "Build All" to restart the whole build process.


        Thorsten

PS: POV-Ray is really not the easiest project to build in MrC, maybe you
should try some of the examples first and get used to the MPW MrC
environment. Once you get more experience it will be less frustrating :-)


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Moon47
Subject: Re: Atempting MPW Compile ?
Date: 11 May 2000 01:19:30
Message: <3918F41C.F5E0B95C@earthlink.net>
<> Yes, they do. config.h gets included via frame.h.

Oh, i see... OK...

<> Oh, and this code should work. Are you sure you removed the three
defines
<> from the right config.h (the one in the MacSource folder)? You may
also want
<> to try "Build All" to restart the whole build process.

Commented out the defines as suggested... Started from scratch... No
change same error w/ converting int to struct file_handle_struct *...???

<> PS: POV-Ray is really not the easiest project to build in MrC, maybe
you
<> should try some of the examples first and get used to the MPW MrC
<> environment. Once you get more experience it will be less frustrating
:-)

Yes i agree this is not the easiest program to start out w/ but i do not
mind the challenge. I hope i am not frustrating you w/ all the questions
i sure you have better things to fill your time. I do appreciate the
help though...

Btw: I tried the CW compile witch did annoy me... It had more
problems... Specifically finding the Zlib and Pnglib files... I know
even less about the CW environment and how to manipulate it so, i will
not be getting in to that at this point.
Although it has some nice features i am impressed with it will take more
time to get use to than to just finish the current MPW project...

TTFN... =)


Post a reply to this message

From: Moon47
Subject: Re: Atempting MPW Compile ?
Date: 11 May 2000 04:09:06
Message: <39191BDD.CC15CB3F@earthlink.net>
OK just finished the CW compile ...
That was too easy what is the fun in that...
It still complained of implicitave (splng) conversion problems but
compiled fine...
One last thing... How can i replace the current patches w/ some
unofficial patches mainly the media and function patches interest me it
would be nice to have these in my compile... The main reason for this
whole venture in the first place... That and to see if i could get a
nice compiled program to begin with...


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Atempting MPW Compile ?
Date: 11 May 2000 13:46:52
Message: <391af20c$1@news.povray.org>
In article <39191BDD.CC15CB3F@earthlink.net> , Moon47 <rdm### [at] earthlinknet>
wrote:

> One last thing... How can i replace the current patches w/ some
> unofficial patches mainly the media and function patches interest me it
> would be nice to have these in my compile... The main reason for this
> whole venture in the first place... That and to see if i could get a
> nice compiled program to begin with...
>

I think Chris Huff mentioned some time ago that he made a compile of MegaPOV
with the official frontend code...


Chris Huff, are you reading this group?


       Thorsten


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Chris Huff
Subject: Re: Atempting MPW Compile ?
Date: 11 May 2000 16:24:54
Message: <chrishuff_99-F16690.15281611052000@news.povray.org>
In article <391af20c$1@news.povray.org>, "Thorsten Froehlich" 
<tho### [at] trfde> wrote:

> I think Chris Huff mentioned some time ago that he made a compile of 
> MegaPOV with the official frontend code...
> 
> Chris Huff, are you reading this group?

Yes. As a matter of fact, I have the .sit file containing that compile 
sitting on my desktop.(I use the official version's interface because I 
couldn't get MacMegaPOV's interface to compile)
I would be happy to e-mail it to anyone who wants it, or maybe I could 
post it to povray.binaries.utilities...

-- 
Christopher James Huff - Personal e-mail: chr### [at] yahoocom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://chrishuff.dhs.org/
TAG Web page: http://tag.povray.org/


Post a reply to this message

From: Chris Huff
Subject: Re: Atempting MPW Compile ?
Date: 11 May 2000 16:26:25
Message: <chrishuff_99-61BABD.15294711052000@news.povray.org>
In article <3918F41C.F5E0B95C@earthlink.net>, rdm### [at] earthlinknet wrote:

> Btw: I tried the CW compile witch did annoy me... It had more
> problems... Specifically finding the Zlib and Pnglib files... I know
> even less about the CW environment and how to manipulate it so, i will
> not be getting in to that at this point.

I would recommend that you use the CodeWarrior project included with the 
Mac source code distribution, instead of starting from scratch. This 
could save you a lot of trouble.

-- 
Christopher James Huff - Personal e-mail: chr### [at] yahoocom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://chrishuff.dhs.org/
TAG Web page: http://tag.povray.org/


Post a reply to this message

From: Chris Huff
Subject: Re: Atempting MPW Compile ?
Date: 11 May 2000 16:28:32
Message: <chrishuff_99-FD692F.15315411052000@news.povray.org>
In article <39191BDD.CC15CB3F@earthlink.net>, rdm### [at] earthlinknet wrote:

> One last thing... How can i replace the current patches w/ some
> unofficial patches mainly the media and function patches interest me it
> would be nice to have these in my compile... The main reason for this
> whole venture in the first place... That and to see if i could get a
> nice compiled program to begin with...

Basically, replace the modified files, add any new files to the project, 
and recompile. I would recommend you just take the whole MegaPOV source, 
it is much less work than separating out those specific patches would be.

-- 
Christopher James Huff - Personal e-mail: chr### [at] yahoocom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://chrishuff.dhs.org/
TAG Web page: http://tag.povray.org/


Post a reply to this message

From: Moon47
Subject: Re: Atempting MPW Compile ?
Date: 12 May 2000 12:41:39
Message: <391AE580.FE4C760D@earthlink.net>
An e mail would be fine or mail if you have posted w/ name of post and
corresponding binary group...

What a supportive group this is... +)..

Chris Huff wrote:

> > Chris Huff, are you reading this group?
>
> Yes. As a matter of fact, I have the .sit file containing that compile
> sitting on my desktop.(I use the official version's interface because I
> couldn't get MacMegaPOV's interface to compile)
> I would be happy to e-mail it to anyone who wants it, or maybe I could
> post it to povray.binaries.utilities...
>
> --
> Christopher James Huff - Personal e-mail: chr### [at] yahoocom
> TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
> Personal Web page: http://chrishuff.dhs.org/
> TAG Web page: http://tag.povray.org/


Post a reply to this message

From: Chris Huff
Subject: Re: Atempting MPW Compile ?
Date: 12 May 2000 17:59:50
Message: <chrishuff_99-53F95C.17031412052000@news.povray.org>
In article <391AE580.FE4C760D@earthlink.net>, rdm### [at] earthlinknet wrote:

> An e mail would be fine or mail if you have posted w/ name of post and
> corresponding binary group...

I didn't really understand the second part...
I will e-mail you a copy(should I send it to rdm### [at] earthlinknet?), and I 
will post a version of MegaPOV 0.5 to povray.binaries.utilities when it 
is released.(hopefully soon next week)

-- 
Christopher James Huff - Personal e-mail: chr### [at] yahoocom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://chrishuff.dhs.org/
TAG Web page: http://tag.povray.org/


Post a reply to this message

From: Moon47
Subject: Re: Atempting MPW Compile ?
Date: 14 May 2000 00:24:15
Message: <391CDBAE.C9567E58@earthlink.net>
Yes send to rdm### [at] earthlinknet... Source too if you have time... ???

Second part is where i was asking for notification ( where & when ) if you
post your version of mega w/ official GUI.

Chris Huff wrote:

> In article <391AE580.FE4C760D@earthlink.net>, rdm### [at] earthlinknet wrote:
>
> > An e mail would be fine or mail if you have posted w/ name of post and
> > corresponding binary group...
>
> I didn't really understand the second part...
> I will e-mail you a copy(should I send it to rdm### [at] earthlinknet?), and I
> will post a version of MegaPOV 0.5 to povray.binaries.utilities when it
> is released.(hopefully soon next week)
>
> --
> Christopher James Huff - Personal e-mail: chr### [at] yahoocom
> TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
> Personal Web page: http://chrishuff.dhs.org/
> TAG Web page: http://tag.povray.org/


Post a reply to this message

From: Moon47
Subject: Re: Atempting MPW Compile ?
Date: 14 May 2000 00:27:57
Message: <391CDC8C.500E1991@earthlink.net>
OK tried this... Replaced the source and core file w/ the mega core file
patches and ran into over 1000 errors before it stopped compiling...???

Chris Huff wrote:

> In article <3918F41C.F5E0B95C@earthlink.net>, rdm### [at] earthlinknet wrote:
>
> I would recommend that you use the CodeWarrior project included with the
> Mac source code distribution, instead of starting from scratch. This
> could save you a lot of trouble.
>
> --
> Christopher James Huff - Personal e-mail: chr### [at] yahoocom
> TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
> Personal Web page: http://chrishuff.dhs.org/
> TAG Web page: http://tag.povray.org/


Post a reply to this message

From: Chris Huff
Subject: Re: Atempting MPW Compile ?
Date: 14 May 2000 02:52:44
Message: <chrishuff_99-1C6181.01561114052000@news.povray.org>
In article <391CDBAE.C9567E58@earthlink.net>, rdm### [at] earthlinknet wrote:

> Yes send to rdm### [at] earthlinknet...

It is on it's way...


> Source too if you have time... ???

The source is the same as what you downloaded...oh, except for one thing 
in frame.h, change this part:
#ifdef GetTicksPatch
  #ifndef CLOCKDIVIDER /*ticks per second */
    #define CLOCKDIVIDER CLK_TCK/*provided by standard c? */

To this:
#ifdef GetTicksPatch
  #ifndef CLOCKDIVIDER /*ticks per second */
    #define CLOCKDIVIDER CLOCKS_PER_SEC

That should be it...

> Second part is where i was asking for notification ( where & when ) if you
> post your version of mega w/ official GUI.

I will post it to either .binaries.utilities or to my web site, I 
haven't decided yet(though my web site badly needs updating). Or I may 
get Mac OS 9 and put it on my iDisk. :-)

-- 
Christopher James Huff - Personal e-mail: chr### [at] yahoocom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://chrishuff.dhs.org/
TAG Web page: http://tag.povray.org/


Post a reply to this message

From: Chris Huff
Subject: Re: Atempting MPW Compile ?
Date: 14 May 2000 02:56:12
Message: <chrishuff_99-9069CD.01593914052000@news.povray.org>
In article <391CDC8C.500E1991@earthlink.net>, rdm### [at] earthlinknet wrote:

> OK tried this... Replaced the source and core file w/ the mega core file
> patches and ran into over 1000 errors before it stopped compiling...???

Did you add the new source files? Like photons.c, postproc.c, etc...
Also, make the modification I suggested to frame.h, which I think was 
found by Thomas Willhalm.
Note that the number of errors is usually unreliable, the compiler often 
keeps going after an error and misreading the code, making perfectly 
good code produce errors. A single typo can cause tens or hundreds of 
"errors".

-- 
Christopher James Huff - Personal e-mail: chr### [at] yahoocom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://chrishuff.dhs.org/
TAG Web page: http://tag.povray.org/


Post a reply to this message

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