|
An idea that just occurred to me:
We have situations in which a source codebase in one library has to be
compiled, *under programmatic control* in other libraries. For
maintenance purposes, we don't want source scattered across the various
target libraries.
Is it possible to (1) set up logicals of source files in the target
libraries, with all the members visible, and (2) use them for compilation?
(I'm about to undertake about a half-hour exercise in manually
recompiling a bunch of stuff in precisely the situation I described, or
I'd research it myself before asking about it.)
--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
