In a message dated 12-0894, Gary Chambers said to David Noon:

>David Noon wrote in a message to Gary Chambers:

GC> Why, apparently, are the resultant .EXE files created by
GC> Borland C++ for OS/2 1.5 so much larger than their CSet/2

 DN> for it. Try using -x- as a compiler option (it's
 DN> case-sensitive). Also, -RT- will switch off RTTI.

>Hi David, and thanks for the reply.  Didn't work.  Still very large. My
>previous message states the different options I tried.

 I missed the start of this thread, but we end up with reasonably small
EXE's with BC++ for OS/2.

We compile and link with the following flags:

    CPPFLAGS=-c -V
    TLFLAGS=-c -m -Toe

 AND, we also use the Borland runtime DLL by linking with the corresponding
import library.  That may be the key.  Also, we have recently added some
-x* parameters to some of our compilers as the compiler/helper functions
added by Borland to destruct objects created dynamically within a procedure
like to crash background threads.

 One thing that I've noticed as libraries trend more towards a DLL
orientation than a statically linked environment:  granularity is
forgotten, or given a low priority at best.  That's "fine" (not
really, tho) for a DLL, but if you're statically linking, you DON'T WANT
800MB of code that will never, ever be executed.

 Nick

.. Speed Kills - Use Windows!
-- MR/2 2.15 #0

--- InterPCB 1.50