Config.Irix.pp 4.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151
  1. //
  2. // Config.Irix.pp
  3. //
  4. // This file defines some custom config variables for the SGI/Irix
  5. // platform. It makes some initial guesses about compiler features,
  6. // etc.
  7. //
  8. // *******************************************************************
  9. // NOTE: you should not attempt to copy this file verbatim as your own
  10. // personal Config.pp file. Instead, you should start with an empty
  11. // Config.pp file, and add lines to it when you wish to override
  12. // settings given in here. In the normal ppremake system, this file
  13. // will always be read first, and then your personal Config.pp file
  14. // will be read later, which gives you a chance to override the
  15. // default settings found in this file. However, if you start by
  16. // copying the entire file, it will be difficult to tell which
  17. // settings you have customized, and it will be difficult to upgrade
  18. // to a subsequent version of Panda.
  19. // *******************************************************************
  20. // What additional flags should we pass to interrogate?
  21. #define SYSTEM_IGATE_FLAGS -D__mips__ -D__MIPSEB__ -D_LANGUAGE_C_PLUS_PLUS -D_MIPS_SZINT=32 -D_MIPS_SZLONG=32 -D_MIPS_SZPTR=32
  22. // Is the platform big-endian (like an SGI workstation) or
  23. // little-endian (like a PC)? Define this to the empty string to
  24. // indicate little-endian, or nonempty to indicate big-endian.
  25. #define WORDS_BIGENDIAN 1
  26. // Does the C++ compiler support namespaces?
  27. #define HAVE_NAMESPACE 1
  28. // How about the typename keyword?
  29. #define HAVE_TYPENAME 1
  30. // Will the compiler avoid inserting extra bytes in structs between a
  31. // base struct and its derived structs? It is safe to define this
  32. // false if you don't know, but if you know that you can get away with
  33. // this you may gain a tiny performance gain by defining this true.
  34. // If you define this true incorrectly, you will get lots of
  35. // assertion failures on execution.
  36. #define SIMPLE_STRUCT_POINTERS
  37. // Does gettimeofday() take only one parameter?
  38. #define GETTIMEOFDAY_ONE_PARAM
  39. // Do we have getopt() and/or getopt_long_only() built into the
  40. // system?
  41. #define HAVE_GETOPT 1
  42. #define HAVE_GETOPT_LONG_ONLY
  43. // Are the above getopt() functions defined in getopt.h, or somewhere else?
  44. #define PHAVE_GETOPT_H 1
  45. // Can we determine the terminal width by making an ioctl(TIOCGWINSZ) call?
  46. #define IOCTL_TERMINAL_WIDTH 1
  47. // Do the system headers define a "streamsize" typedef? How about the
  48. // ios::binary enumerated value? And other ios typedef symbols like
  49. // ios::openmode and ios::fmtflags?
  50. #define HAVE_STREAMSIZE
  51. #define HAVE_IOS_BINARY
  52. #define HAVE_IOS_TYPEDEFS
  53. // Can we safely call getenv() at static init time?
  54. #define STATIC_INIT_GETENV 1
  55. // Can we read the file /proc/self/environ to determine our
  56. // environment variables at static init time?
  57. #define HAVE_PROC_SELF_ENVIRON
  58. // Do we have a global pair of argc/argv variables that we can read at
  59. // static init time? Should we prototype them? What are they called?
  60. #define HAVE_GLOBAL_ARGV 1
  61. #define PROTOTYPE_GLOBAL_ARGV 1
  62. #define GLOBAL_ARGV __Argv
  63. #define GLOBAL_ARGC __Argc
  64. // Can we read the file /proc/self/cmdline to determine our
  65. // command-line arguments at static init time?
  66. #define HAVE_PROC_SELF_CMDLINE
  67. // Should we include <iostream> or <iostream.h>? Define PHAVE_IOSTREAM
  68. // to nonempty if we should use <iostream>, or empty if we should use
  69. // <iostream.h>.
  70. #define PHAVE_IOSTREAM
  71. // Do we have a true stringstream class defined in <sstream>?
  72. #define PHAVE_SSTREAM
  73. // Does fstream::open() require a third parameter, specifying the
  74. // umask?
  75. #define HAVE_OPEN_MASK 1
  76. // Do we have the lockf() function available?
  77. #define HAVE_LOCKF 1
  78. // Do the compiler or system libraries define wchar_t for you?
  79. #define HAVE_WCHAR_T 1
  80. // Does <string> define the typedef wstring? Most do, but for some
  81. // reason, versions of gcc before 3.0 didn't do this.
  82. #define HAVE_WSTRING 1
  83. // Do we have <new>?
  84. #define PHAVE_NEW
  85. // Do we have <io.h>?
  86. #define PHAVE_IO_H
  87. // Do we have <malloc.h>?
  88. #define PHAVE_MALLOC_H 1
  89. // Do we have <alloca.h>?
  90. #define PHAVE_ALLOCA_H 1
  91. // Do we have <locale.h>?
  92. #define PHAVE_LOCALE_H 1
  93. // Do we have <minmax.h>?
  94. #define PHAVE_MINMAX_H
  95. // Do we have <sys/types.h>?
  96. #define PHAVE_SYS_TYPES_H 1
  97. #define PHAVE_SYS_TIME_H 1
  98. // Do we have <unistd.h>?
  99. #define PHAVE_UNISTD_H 1
  100. // Do we have <utime.h>?
  101. #define PHAVE_UTIME_H 1
  102. // Do we have <dirent.h>?
  103. #define PHAVE_DIRENT_H 1
  104. // Do we have <sys/soundcard.h> (and presumably a Linux-style audio
  105. // interface)?
  106. #define PHAVE_SYS_SOUNDCARD_H
  107. // Do we have <stdint.h>?
  108. #define PHAVE_STDINT_H
  109. // Do we have RTTI (and <typeinfo>)?
  110. #define HAVE_RTTI 1
  111. // The Irix compiler doesn't support the modern STL allocator.
  112. #define USE_STL_ALLOCATOR
  113. // The dynamic library file extension (usually .so .dll or .dylib):
  114. #define DYNAMIC_LIB_EXT .so
  115. #define BUNDLE_EXT