On 26/11/2015 10:11 AM, Jack J. Woehr wrote:
Charles Mills wrote:
Touché.
Yes, yes, I know, I should be using make. We all have a little bit of
dinosaur blood in us. Some are stuck in assembler.
I love assembler. When in assembler, I'm doing it your way.
I don't share your love. I much prefer a compiler to find my bugs for
me. Although I appreciate it's relevance on z/OS where so many system
calls have macro interfaces.
I happen to be stuck in batch JCL compiles. I should learn make but
it is never at the top of the critical path.
I know the feeling. I'd love to play with z/OS more, have access, but
same issue.
1. Will make in fact solve this specific problem? Can one readily
specify "global" compiler options for most modules and override them
for specific modules?
Not exactly. #pragma is #pragma and sometimes you just have to bite
the bullet and manually surround preprocessor directives with platform
#ifdefs
#ifndef __Z_OS__ /* or whatever is the platform tag for you */
#pragma(foo)
#endif
Classic porting_software_to_myPlatform() pain in the butt. Welcome to
the club. I do it all the time because I'm on one of the less popular
open source operating systems
and have to constantly participate in our community porting process.
But once can use make and macros to do all sorts of things that can
accomplish what you are trying to achieve.
2. What's a good learning source for make?
www.oreilly.com/openbook/make3/book/index.csp ?
That's a real good start. That's GNU make, by the way, which is way
advanced over Sys V make. So the make command you have on your system
may have issues with some things that work with GNU.
Happy Thanksgiving! I'm thankful that both hardware platforms and
software tools work so much better than they did 30 years ago :)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
