OpenEuphoria

Re: OpenWatcom

• Posted by Matt Lewis <matthewwalkerlewis at gmail.com> Nov 29, 2006
• 515 views

Jason Gade wrote:
> 
> Robert Craig wrote:
> > 
> > Matt Lewis wrote:
> > > I committed some changes to the Euphoria svn repository to fix the source 
> > > for OpenWatcom.  There's also a makefile (makefile.wat) for building 
> > > it using OpenWatcom.
> > 
> > Good. I can compile with OpenWatcom, but
> > I still normally use Watcom 10.6 because
> > of the "pop up to full screen" issue in DOS.
> > I'm glad there's a developer using OpenWatcom.
> > I see you added "EOW". 
> > 
> 
> Sorry if the last message shows up; I meant to quote.
> 
> What's EOW? That has been bugging me all day.
> 

If you've looked at the source, you've probably noticed several macros
that identify the platform and compiler being used.  There are a couple 
of places that need to be different from Watcom 10.6 vs Open Watcom 1.5
(be_callc.c and be_runtime.c).  I added a new macro (EOW) to specify
that the OpenWatcom compiler is being used.  The convention that Rob has
used is to prefix any of his macros with an 'E', so I used that, too.

The makefile is handy, because it only compiles the files that have been
changed.  If you make changes to the front end, you may need to change the
makefile.  The translator will break up large files, and changes (additions,
deletions, etc) may produce different files.  Basically, if any of the 
euphoria source files for the front end change, it will run the translator,
but only recompile those files that would be affected by the changes.

Also, if you build the translator and then want to build the interpreter
(or vice versa), you should make clean (wmake -f makefile.wat clean).
They take a slightly different combination of files (some files are 
in one but not the other, and different routines get deleted, leaving 
different file sizes).

Matt