eap@bu-pub.bu.edu (Eric A Pearce) (02/06/91)
How have people been getting all these compilers to co-exist on the same system ? This would be on a Sun running SunOS 4.1. Sun 4.1 cc GNU gcc 1.38.90 GNU g++ 1.37.2 ATT C++ 2.1 This is what I've done in /usr/include/sys/stdtypes.h #ifdef __cplusplus typedef unsigned int size_t; #else #ifdef __GNUC__ typedef unsigned long size_t; #else typedef int size_t; /* ??? */ #endif #endif #if defined (__GNUG__) || (__GNUC__) typedef long int ptrdiff_t; #else typedef int ptrdiff_t; #endif Is there a cleaner way to do this? -e -- ------------------------------------------------------------------------------- Eric Pearce eap@bu-pub.bu.edu Boston University Information Technology 111 Cummington Street, Boston MA 02215 617-353-2780 voice 617-353-6260 fax
steve@taumet.com (Stephen Clamage) (02/07/91)
eap@bu-pub.bu.edu (Eric A Pearce) writes: >How have people been getting all these compilers to co-exist on the same >system? ... [several C and C++ compilers listed] >This is what I've done in /usr/include/sys/stdtypes.h [ uses #ifdef's to get the typedefs needed for the various compilers ] >Is there a cleaner way to do this? Apart from being ugly, it makes adding a new compiler or updating an existing one very difficult. We solve the problem by using a different include file directory tree for each compiler. The standard system includes would usually be in /usr/include, for example. When you add the XYZ compiler, put its supplied include files in /usr/local/XYZ/include. When you use the XYZ compiler, configure it to search /usr/local/XYZ/include first, then /usr/include. This causes problems when you need a standard system include which conflicts with the XYZ compiler's include files. You then add a customized version of the system include file to the XYZ include directory tree. In your example, you would have a version of stdtypes.h in /usr/local/XYZ/include/sys customized for the XYZ compiler. -- Steve Clamage, TauMetric Corp, steve@taumet.com