2006-07-10 19:13:34 +02:00
|
|
|
These utilities help clean up #include file usage. They should be run
|
|
|
|
|
in this order so that the include files have the proper includes before
|
|
|
|
|
the C files are tested.
|
2000-06-15 00:28:16 +02:00
|
|
|
|
|
|
|
|
pgfixinclude change #include's to <> or ""
|
2000-06-15 00:33:06 +02:00
|
|
|
|
|
|
|
|
pgcompinclude [-v]
|
|
|
|
|
report which #include files can not compile on their own
|
2000-06-15 00:28:16 +02:00
|
|
|
|
2006-07-10 19:13:34 +02:00
|
|
|
pgrminclude [-v]
|
|
|
|
|
remove extra #include's
|
|
|
|
|
|
2006-07-15 05:27:42 +02:00
|
|
|
pgcheckdefines
|
|
|
|
|
check for #ifdef tests on symbols defined in files that
|
|
|
|
|
weren't included --- this is a necessary sanity check on
|
|
|
|
|
pgrminclude!
|
|
|
|
|
|
2000-06-15 00:28:16 +02:00
|
|
|
pgdefine create macro calls for all defines in the file (used by
|
|
|
|
|
the above routines)
|
|
|
|
|
|
2006-07-11 21:52:12 +02:00
|
|
|
It is also a good idea to sort the pg-specific include files in
|
|
|
|
|
alphabetic order. This is best done with a text editor. Typical usage
|
|
|
|
|
order would be:
|
|
|
|
|
|
|
|
|
|
pgfixinclude
|
|
|
|
|
pgcompinclude
|
|
|
|
|
pgrminclude /src/include
|
|
|
|
|
pgcompinclude
|
|
|
|
|
pgrminclude /
|
2006-07-15 05:27:42 +02:00
|
|
|
pgcheckdefines
|
