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 [ 23 | February | 2003 ]

<< Previous Message <<


Date: Sun, 23 Feb 2003 21:41:32 PST8
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: Open Source file tree ?

In <3E59221B.4DDD@peterskye.com>, on 02/23/03
at 11:33 AM, Peter Skye said:

>I don't understand how to organize the file tree. I'm familiar with the
>bin doc src subdirectories but I don't know if there's a specification on
>how the containing directory is to be placed.

Not really, although I tend to place each application within a single
top-level container directory. It makes them easy to find and it makes it
somewhat easier to share common components. For example:

dev2
app1
app2
app3
h
lib
tools

>What should the development tree look like (including the various
>utilities required for make/compile), and what should the user's

The utilities themselves live in their own installation directories. Then
there are the wrappers I use to automate repetitive functions. Depending
on how many there are, I many have a project tools directory or I may just
dump them into my default \cmd or \bin directories.

The key with all of this is to be consistent. Netlabs is pretty good this
way, as are unix apps. That way you can leverage what you learn from one
on the next.

>execution tree look like (or are the development tree and the execution
>tree one-and-the-same)?

There's no need for any relationship. That one of the reasons a good
makefile always has a 'make install' target.

Steven

--
---------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.35 #10183 Warp4/FP15/14.085_W4
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-programming".

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

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


<< Previous Message <<

Return to [ 23 | February | 2003 ]



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.