Unix Program Paths

Although it is possible to place command paths for all Unix/Linux variants in this unixcmds_macros.cfg file (indeed, in the top-level macros.cfg), we suggest that you confine command-path macros for each operating system in their own, separate #include files as shown.

///////////////////////////////////////////////////////////////////////////////
// 
// unixcmds_macros.cfg -- Unix command and program paths
// 
///////////////////////////////////////////////////////////////////////////////
// 
// this include file is standard; only edit as described below
// 
///////////////////////////////////////////////////////////////////////////////
// 
// there are several ways to organize the unix command macros; one way is
// to list the commands, one after the other, in a single file like so:
// 
// awk
// #if solaris
//         /bin/awk
// #elif linux  
//         /usr/bin/awk
// #endif
// 
// chown
// #if solaris
//         /bin/chown
// #elif
//         /bin/chown
// #endif
// 
// ...
// 
// doing it this way helps ensure that a command macro is defined for
// each operating system; but, it requires a lot of #if-#endif statements,
// and requires expunging numerous #if or #elif clauses if you don't need
// to support one or more operating systems
// 
// a better way is to isolate the macro defs in a separate include file for
// each operating system (albeit at some risk that a command might not be
// defined across all operating systems); for example, a solaris include file
// would list all macro defs for that operating system within a single
// #if-#endif structure like so:
// 
// #if solaris
// awk             /bin/awk
// chown           /bin/chown
// ...
// #endif
// 
// now, if you don't need the macro defs for a particular operating system,
// simply comment out the #include line following, or remove it altogether
// 
///////////////////////////////////////////////////////////////////////////////
// 
// in each of the following macro include files, we tried to list the unix
// commands you might use in a PIKT script; more commands will be added to
// each include file as needed
// 
// comment out unneeded includes per site requirements
 
#include <macros/adm/unixcmds_suse_linux_macros.cfg>
#include <macros/adm/unixcmds_redhat_linux_macros.cfg>
#include <macros/adm/unixcmds_debian_linux_macros.cfg>
#include <macros/adm/unixcmds_solaris_macros.cfg>
#include <macros/adm/unixcmds_aix_macros.cfg>
 
// and so on for other unix/linux variants...
 
///////////////////////////////////////////////////////////////////////////////

For more examples, see Samples.