Path: utzoo!utgpu!attcan!uunet!tut.cis.ohio-state.edu!ucbvax!agate!apple!sun-barr!newstop!sun!quintus!jbeard
From: jbeard@quintus.UUCP (Jeff Beard)
Newsgroups: comp.software-eng
Subject: Re: Do people really use Make?
Message-ID: <1241@quintus.UUCP>
Date: 11 Aug 89 17:24:22 GMT
References: <634@orange.qtp.ufl.edu>
Reply-To: jbeard@quintus.UUCP (Jeff Beard)
Organization: Quintus Computer Systems, Inc: Mountain View, Ca
Lines: 28


Instead of porting make and the requisite makefile to each Target system, 
have the master makefile generate "command steams".

The single source control is a requirement, but you've already got that defined.

The scenario goes like this,

	master source file modifiaction(s).

	make -n Target_name >Target.cmd_stream

	upload Target.cmd_stream to Target system 

	execute cmd_stream

Don't try to emit the precise command sequence per se.   JCL or CLIST streams
for MVS are a B*T*H.  Even VM/370 EXECs or VMS scripts can be too.
Instead, define a macro/meta approach that allows the target system total 
freedom of implementation, eg:  'devupd proc source_name_1'
for each file to be processed.

devupd is a master procedure to process arguments and create a job/command
 sequence intended.

arg proc is a generic label for 'what to perform', compile, load, update,...

arg source_name_1 is the file to be processed by 'proc'.