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 13:03:45 PST8
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: OpenWatcom setup (was: call(TZ) ? - C)

In <402E6F2F.367E@peterskye.com>, on 02/14/04
at 10:56 AM, Peter Skye said:

>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?

That was the case at one time. If anything like this still exists, it
probably nothing you will ever use. :-)

>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\

That's essentially what I have, although I organize the source code a bit
differently since I have a lot that's not neccessarily related.

My trees look like:

\sla_dev\proj1
...
\sla_dev\proj2
\client1
...
\clientn

Shared stuff is in:
\lib
\lib2
\libw2
\include

and so on.

Each project directory will have whatever it needs from:

.\src
.\doc
.\bld
.\rel

and so on.

The structure does not matter as much as the consistency. I often need to
find things years later.

>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?

This works fine for command line stuff.

>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?

See above.

>I can't organize by project since almost everything is related to one
>project.

Sure you can. You get to define what a project is. You can always
organize by component. This is true even if the components are only
logical components and you build to to single exe. Makefiles handle all
of this easily enough.

Regards,

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.41 #10183 Warp4/FP15/14.093c_W4
www.scoug.com irc.webbnet.info irc.fyrelizard.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-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.