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-HELP Mailing List Archives

Return to [ 25 | October | 2008 ]

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


Date: Sat, 25 Oct 2008 18:17:34 -0700
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Building flipit (was GCC432)

In <20081025163928-53148-7@scoug.com>, on 10/25/08
at 04:39 PM, "Robert Blair" said:

>> >GLIBIDL335, and AUTOCONF.
>>
>> Look around. It's very unlikely that Paul did not include it. The
>> settings exist because some apps will require a specific AUTOCONF version.

>I found them on eCS cd 2. Paul may have thought that if you were going
>to use his buildenv you would have them installed.

I don't think so.

Autoconf is installed in /usr/bin in Paul's zip, so AUTOCONF=d:/usr would
work. However, since /usr/bin will be in the PATH you don't need to set
AUTOCONF.

>I assume that I need to change the d: to f: and the locations (the
>location of some files are different than what is in the buildenv) of
>some files and put them in some directory.

Yes. As the title lines say, these are generic scripts.

>I do not have any *_shl files

You wouldn't. My initials are SHL and I name the scripts this way so I
can find them easily in directories that contain lots of OP's code.

>anywhere so where do I put these files.

Put then in the top level directory of whatever app you are building.
They can go anywhere, but since they are application specific, this is the
best place for them.

The supporting scripts, such as gcc335env.cmd are generic, they should
live in a common directory in the PATH. Mine live in d:\cmd.

>One zip had init_shl and init_shl.cmd.

These are updates to the originals. Notice they claim to be specific to
flipit.

>The other zip had cfg_shl, gcc335env.cmd, gnudevenv.cmd, init_shl,
>initshl.cmd, and m_shl.

These are the generic originals, plus a subset of the supporting scripts.
They were intended to show you how I have things organized. Your version
of init_shl.cmd can probably just call your version of Paul's gcc335.cmd.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 3.00.11.18 BETA #10183 eCS/Warp/DIY/14.103a_W4 etc.
www.scoug.com irc.ca.webbnet.info #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
"postmaster@scoug.com".

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


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

Return to [ 25 | October | 2008 ]



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.