Re: powercobol compile all directory projects
- From: donald tees <donald@xxxxxxxxxxxxx>
- Date: Tue, 10 Apr 2007 12:49:34 -0400
Pete Dashwood wrote:
Will it accept wildcard operands... ?Do not know, as I have never tried it. However, I can see two problem doing it the way you suggest.
NMAKE *.MAK > LPT1:
First of all, the entire point of the batch file is to do things in a specific order. The first project creates rep files and object libraries required for the second, etc. That is the main problem with Pstaff. The damed thing sorts into alphabetical order, and there is no way to force a specific order except doing it manually, one DLL at a time.
The approach is fubar for OOP stuff, as inheritance levels etc. are completely discarded. Thus I split the main project up into sub-projects, and compile them in order.
Secondly, I do that when I am testing ... if the compile finishes, I proceed to the install step, and sometimes even end the batch file with a CD to the run area and execution.
NMAKE *.mak may work for a small collection of independent programs, though. I'll try it later.
Donald
.
- References:
- powercobol compile all directory projects
- From: ramzenit
- Re: powercobol compile all directory projects
- From: Jeff Campbell
- Re: powercobol compile all directory projects
- From: ramzenit
- Re: powercobol compile all directory projects
- From: donald tees
- Re: powercobol compile all directory projects
- From: Pete Dashwood
- powercobol compile all directory projects
- Prev by Date: Re: Conversion of data & associated logic from ISAM to RDB
- Next by Date: Re: Conversion of data & associated logic from ISAM to RDB
- Previous by thread: Re: powercobol compile all directory projects
- Next by thread: Re: powercobol compile all directory projects
- Index(es):
Relevant Pages
|