MF>     I am trying to get Guidelines v2.1a to generate code which will
  >compile with Borland C++ for OS/2 v1.5.  I created a very simple
  >application (as per the tutorial in the docs), generated code without any
  >problem, but I am unable to compile.  First off, MAKE claims it's unable to
  >run BRCC.  This is no problem, so I go into the directory where the source
  >code is located and try 'MAKE -f PROGRAM.MAK' (where PROGRAM.MAK is the
  >makefile that Guidelines generated).  While it's compiling, I also get an
  >'unable to find OS2STUB.EXE' error.  From looking at other *.DEF files, I
  >see this is commented out, so I do the same.  Final linking takes place and
  >I get several unresolved externals for the various functions that
  >Guidelines uses.  (It appears that the header file guirun.h) isn't being
  >compiled in properly.

Gee, glad to see I'm not the only one!!!  I've already sent Jon a letter
dealing with these problems (at least with the inability to run any of
the compilers from within Guidelines.  BRCC is not the only one that
"cannot be run".) and I await a response.
  Ok, first of all, the OS2STUB.EXE is VERY easy to take care of.  If
you have a DOS compiler, simply create your own stub and place it in the
..\SRC directory.  It will be sent in as the OS/2 stub and be used for
all your programs.  You could personalize this one, but I'll be the
first to tell you that I NEVER could get it to work with a personalized
one! (As a second, and probably better resort, you could use the
OS2STUB.EXE that comes with the OS/2 toolkit.  I can't believe Borland
didn't provide it with this one.  It seems that they think we have
control of everything.  Sure, it's nice that they AUTO include one, but
they don't take into consideration programs like Guidelines which
doesn't give us control of whether or not the statement is added or
not.)  NOTE: THIS HAS ALREADY BEEN REPORTED TO GUIDELINES TECH-SUPPORT
AND THEY INFORMED ME THAT THEY REALIZED IT -=ONLY=- WHEN IT WAS TOO
LATE.
  I, too, have been getting the unable to resolve externals with Borland
C++ v1.5.  It seems we bought into a compiler that can't do jack.  Let
me tell you now that I HAD been using Guidelines happily with Borland
C++ v1.0 for a while now, and yesterday when I installed v1.5, these
errors began occurring.  Rest assured, these are not problems with
Guidelines, only with Borland (as far as I can discern).
  Run a test with the IDE, compile a function to an OBJ format.  Then
compile a project with the OBJ file included in the project to an EXE.
It should give you the same problem with unresolved externals as well as
the problem with "Bad field list in debug information in module
MODULE.OBJ".  Borland has done it again!

MF>  Before anybody asks, yes, I have the compiler set for Borland
  >  C++ for OS/2 and have all of the file pathes and such set as they
  >  should be.

I have no doubt...  It's a problem with Borland C++ v1.5 (even by itself
these problems occur).

MF>     Any help would be greatly appreciated!  I know everybody loves this
  >new tool, but I just can't get it working properly on my system.

I wouldn't say everybody, there are a few that grumble.  But yes, I
loveD it...  Now all my programming has come to a dead stop.

MF>Thanks in advance!

No problem

MF>Mike.

Mike.
___
 .Mike's Mail Internet:   MICHAEL.DOUGLASS{at}LCHANCE.SAT.TX.US

--- Maximus/2 2.01wb