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 [ 14 | February | 2004 ]

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


Date: Sat, 14 Feb 2004 10:56:01 PST8
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: OpenWatcom setup (was: call(TZ) ? - C)

Content Type: text/plain

Steven Levine wrote:
>
> >would have needed to find os2.h.
>
> Why would that be a problem? gcc has had
> everything needed to do OS/2 apps for years.

Oops, found it, thanks. It was pgcc that didn't have os2.h.

> >I think I'm supposed to copy something out of [my
> >Watcom 11] into the Open Watcom installation.
>
> I think your memory is incorrect here. OpenWatcom
> has everything needed to do OS/2 apps.

I thought there were some libraries in Watcom 11 which were owned by a
third party and couldn't be distributed with OpenWatcom, but if you
owned Watcom you could copy the libraries to your OpenWatcom
installation. Was that only for device driver stuff? Were the
libraries rewritten?

Anyway, how do you recommend setting up the OpenWatcom directory
structure and my C source code? I've come around to your way of
thinking on PATH stuff -- don't put it in CONFIG.SYS, but instead use a
.cmd to set up the path. Since I also might want to use gcc and pgcc,
would the following work?

\emx\
\pgcc\
\OpenWatcom\
\mysource.c\

Then I could use .cmd files named cEMX.cmd, cPGCC.cmd and cOW.cmd to
compile the C source with whichever compiler I wanted. Yes?

I currently put all my sources in a single \skye.SRC\ directory and I
compile into the same directory, and when I have something that tests
okay I move it to my \skye.EXE\ directory. But it's getting a little
messy having all the sources in one directory -- any recommendations? I
can't organize by project since almost everything is related to one
project.

- Peter

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

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
"rollin@scoug.com".

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


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

Return to [ 14 | February | 2004 ]



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.