SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Thu, 3 Jan 2002 19:06:12 PST7
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: Device driver

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

In <3C34E406.4036755E@attglobal.net>, on 01/03/02
at 06:06 PM, Harry Chris Motin said:

>> 1. You have reference to a toolkit, residing on D:\. What toolkit is
>> this? Is it the IBM device drivers kit?

This is actually the Warp4.5 Toolkit. The same technique will work for
for the DDK. The files are just in a different place. d:\ddk on this box.

>> 2. Also, you state: "To use Watcom, run this before running your app".
>> Yes, run the command file. But, before running what app??

Any app that depends on these settings to find what it needs to work
correctly. For example, the compiler or the linker or whatever

Typically, would will not invoke the individual apps from the command
line. You would control the build process with a makefile. This makes
the process repeatable. It also means some of the setting in the .cmd
file could just as well be made within the makefile. Makefiles come in
various levels of complexity. Here's one that build one of my utilities
with some annotations:

.SUFFIXES:
.SUFFIXES: \
.cpp .obj

# This is an implicit rule stating how to build an arbitrary .obj from the
associated .cpp .cpp.obj:
@echo " Compile::C++ Compiler "
icc.exe /Ti /C %s

# This say we are going to build utimemdy.exe as the final product. all:
.\utime2mdy.exe

# This says build utime2mdy.exe whenever utime2mdy.obj or slalib.lib or #
utime2mdy.mak change
# The build instructions are explicit
.\utime2mdy.exe: \
.\utime2mdy.obj \
d:\sla_lib2\slalib.lib \
utime2mdy.mak
# Runs the linker
icc.exe @<<
/Feutime2mdy.exe
d:\sla_lib2\slalib.lib
.\utime2mdy.obj
<<

# This says build utime2mdy.obj whenever utime2mdy.cpp or utime2mdy.mak
change # The build instructions are implict and will use the cpp.obj rule
defined above .\utime2mdy.obj: \
utime2mdy.cpp \
utime2mdy.mak

This one uses VAC to build a C++ app. Changing it to use Watcom is
trivial. The dependecies don't change. Just the command names and the
switches would need to change. icc would change to wcc and wlink and so
on. We could spend more time talking about how to do it than it would
take to just do it.

The nice thing about makefiles is once you have built one for a project it
tends to become invisible and needs little maintenance.

Steven

--
----------------------------------------------------------------
"Steven Levine" MR2/ICE 2.30a #10183 Warp4/FP15
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
----------------------------------------------------------------

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 03 | January | 2002 ]

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.