SCOUG-Programming Mailing List Archives

<< Previous Message <<

Date:	Thu, 27 Oct 2005 09:43:36 PDT7
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-programming@scoug.com
To:	scoug-programming@scoug.com
Subject:	SCOUG-Programming: WPS programming with Watcom (was Undeliverable Mail)

Content-Transfer-Encoding: 7bit

In <20051027051821-62211-8@scoug.com>, on 10/27/05
at 05:18 AM, "Harry Motin" said:

>So I already reference both the JAVA and the OS/2 toolkit libraries. I'm
>told (or, I believe that I understand) that, if I use more than one
>compiler on my system, I should use a batch file, and not the
>CONFIG.SYS, to set these variables. Is that right?

This is correct. In most cases, a setup script makes life simpler because
it avoids conflicts. There's also a minor performance boost because you
can optimize the environment for the specific toolchain.

As the attached sample scripts show, the configuration process can be
simple or relatively complex, depending on the task at hand. The setup
for OpenWatcom is easy. The setup for building Mozilla is a bit more
complex.

Keep in mind that when IBM installs an app and updates config.sys, it is
doing a simple, generic install with relatively minimal consideration for
how the results might conflict with apps that it does not control. This
approach makes sense because it difficult to test what one does not know
exists. It is up to us to use our common sense and decide if the IBM
method makes sense in our specific environment.

Regards,

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67 #10183 Warp4.something/14.100c_W4
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
----------------------------------------------------------------------

File attachment: Watcom.cmd

File attachment: mozdev.cmd

Return to [ 27 | October | 2005 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.