Can glib-config or gtk-config support multiple compilation systems?

[jlw caldera com (John Wolfe)]

I am beginning a port/build of the Mozilla 1.2.1 release for 
UnixWare 7.1.3 and of course need to build glib and gtk+
in order to build mozilla.

I have no problems building all 3 products with a single 
set of compilation tools.  I can restrict the released material
to include just the glib and gtk+ runtime libraries that are
needed by mozilla.

Ideally, I would like to release the gtk+ as a "supported"
development tool on UnixWare 7.1.x, but I foresee a major
stumbling block with glib-config and gtk-config on a system
where there may be 3 separate compilation systems - each with
different compilation/link flags

On UnixWare, we have 2 supported compilers:

                        ccflags                   ldflags

   "native" cc        -Kthread                    -Kthread
                      -Kpthread                   -Kpthread

   "supported" gcc    -pthread                    -pthread
      2.95.3  

  where -Kthread and -pthread are effectively a -D_REENTRANT on compilations
  and a -l<thread> at the correct position on link command.

and numerous unsupported compilers such as user built gcc releases
where:

   ccflags = -D_REENTRANT
   ldflags = -lpthread
   

The glib and gtk+ libraries consist of C source code and the ABI is
the same for all compilers.  One set of runtime would work for all
compilers, but the xxx-config scripts would not.  A single xxx-config
script would only return the flags that work with the C compiler used
to build glib or gtk+, not the compiler being used to build products
X, Y or Z.

Typically the configure scripts for product X would set the appropriate
CCFLAGS or LDFLAGS based on the compiler being used - CC=/usr/gnu/bin/gcc
or CC=/usr/ccs/bin/cc.  Given, the configure.in may need to be tweaked
and while that is not ideal, it is better than getting the incorrect set
of flags as reported by a single compiler unaware glib-config script.

Have you given this problem any consideration? 

Is there a way to support multiple compilers with one instance of the Gimp 
development toolkit that I have not seen?


-- John Wolfe       (jlw at sco  dot com)