SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 05 | September | 2005 ]

>> Next Message >>


Date: Mon, 5 Sep 2005 23:28:51 PDT7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: Re: Using the Watcom IDE and Products

In <200509042240.1ec6Ui5zh3Nl34f2@mx-roseate.atl.sa.earthlink.net>, on
09/04/05
at 07:40 PM, "Harry Motin" said:

I'm moving this to scoug-programming so that others can participate and/or
learn.

>Now, howeve, I have some code that uses variable types and other stuff
>contained in the IBM Developer's Toolkit (the one that comes on the eCS
>CD, the OS2TK45 product). When I try to link and compile this code, the
>IDE tells me that I have some unknown variable types in my code (like
>"WPProgram" and "PPROGDETAILS"). I think the problem is that Watcom does
>not know about the OS2TK45 libraries.

This is mostly true. The Toolkit headers supplied with the the current
version of Watcom are not 100% complete relative to those supplied with
the OS/2 Toolkit.

The solution, as you suspect is to use the is to use the OS/2 Toolkit
headers. Watcom like most other compilers understands the INCLUDE
environment variable. Set this up so that the Toolkit include directories
appear first and you should get a clean compile.

The Watcom C/C++ User's Guide explains the gory details.

You might still get some link errors. If you you will need to locate the
import libraries that define the missing symbols and specify them to the
link instructions.

>I'm a little puzzled by this, because I thought I had the
>correct variables set in my CONFIG.SYS file.

Well, it this was the case, you would not be getting errors.

I recommend you use a cmd cmd file to initialize the variables and invoke
the IDE. This will make you testing go much faster.

Regards,

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67 #10183 Warp4.something/14.100c_W4
www.scoug.com irc.fyrelizard.com #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-programming".

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

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


>> Next Message >>

Return to [ 05 | September | 2005 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.