[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | USG buildhelp questions/answers |
|
Moderator: | SMURF::FILTER |
|
Created: | Mon Apr 26 1993 |
Last Modified: | Mon Jan 20 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2763 |
Total number of notes: | 5802 |
222.0. "how to build a library for internal use only?" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Mon Jul 19 1993 18:03
Date Of Receipt: 19-JUL-1993 14:49:45.56
From: ABYSS::jtkohl "John Kohl"
To: abyss::buildhelp
CC:
Subj: how to build a library for internal use only?
I'd like to build a library to be used by a few programs (to
consolidate code in a single place), but which need not appear on the
final kits.
How would I create Makefiles to do this? Are there examples?
I actually have two cases: one for a library of code provided by
another group not at ZKO, and one for a library of code I'm
yanking out of programs and into a common source file. The former case
really needs to be a library; the latter case would work fine as a
shared .c file with VPATH magic, I guess, but it'd be nice to know how
to build such a library if desired.
Thanks,
John
T.R | Title | User | Personal Name | Date | Lines
|
---|