Re: iSeries Projects 'Create compile command'

Adam Glauser wrote:

Buck wrote:

Sorry for being so terse. There are 7 of us all told and two of us use WDSC and I'm the only one who uses COMPILE (well my own antique home grown version. I ought to go get Alan's.) The others tend to use PDM option 14 which means that I need to keep my source exactly compatible with their habits.

First I should say that I'm not actually a COMPILE user yet, mainly due to the same reason as you. It just occurred to me that because the COMPILE commands are just comments, it shouldn't be a problem for me to start using it if no one else does. Can a COMPILE user confirm this?

That's absolutely true. For this particular problem (that of the wrong compile command being remembered by WDSC) jamming everything through COMPILE would work because I wouldn't have anything except the actual CRT command in the comments.

But where I to actually use COMPILE for its actual purpose as a preprocessor, the PDM 14 people would not get the same compilation I would. Ick.

I believe that Alan recently added a feature to allow the COMPILE 'script' in a source member to specify which objects that member depends on. IIRC, the command is CHECKOBJ or something like that. So if I followed the documentation correctly, in your LF case you would put something along these lines in your source member:

// CHECKOBJ *LIBL/LOGICAL1
// CHECKOBJ *LIBL/LOGICAL2
// CRTRPGMOD *LIBL/MODULE

And that is wicked cool. Just like MAKE! I can't really argue against using it... I'll see if I can get it put together. Reminds me of David Morris' work with ant for RPG all those years ago.
--buck